ladle

Patch Changes

• #198 3c8b35c Thanks @tajo! - Fix missing --stories flag for ladle build.

• #198 3c8b35c Thanks @tajo! - Don't replace user provided css.postcss in config

Patch Changes

• #196 f92ed78 Thanks @tajo! - Fix some CSS sync issue when switching into iframed version.

Major Changes

• #191 3209be6 Thanks @tajo! - Upgrade to Vite 3. It should not be really a big breaking change for Ladle but we expose the whole vite.config.js so you might run into some deprecations. Read more to see if this could impact you.

  Vite 3 also ships as ESM module. That forces us to stop distributing @ladle/react-cjs. We used it for our internal yarn pnp setup but we don't need it anymore. Pure ESM everywhere!

Minor Changes

• #194 63c8821 Thanks @tajo! - Bump all repo dependencies do the latest and abondon cjs build&publish.

Patch Changes

• #191 3209be6 Thanks @tajo! - Uses hook version for iframe window ref to prevent some re-renders. Fix viewport when navigating from a different story.

• #193 e573adc Thanks @tajo! - Improve the kebab casing of story names to convert MapSDK into map-sdk and not map-s-d-k.

• #194 63c8821 Thanks @tajo! - Add margin 0 to iframe's body just as Stackblitz workaround

• #191 3209be6 Thanks @tajo! - Find a free port for HMR server. Before, if there were multiple instances of Ladle, the client would always connect to the initial HMR server and reloads didn't work.

Minor Changes

• #190 21959e9 Thanks @tajo! - Add addon-width and iframe mode. You can set meta.width and meta.iframed to render stories inside of an iframe. This is useful for testing responsivness or components like modal that take full screen.

• 1745a95 Thanks @talshani! - Add support for native Windows.

Patch Changes

• #188 2f142cc Thanks @pdeslaur! - Fix compatibility issue with resolve.alias vite config to fix issue tajo/ladle#187.

• #187 ebb1923 Thanks @tajo! - Move background color to negative zindex to support cases when components use some negative zindexes as well.

• #189 f84bbde Thanks @tajo! - Improve the performance of virtual stories modules. fs.promises.readFile much slower than fs.promises.readSync and it blocking CPU doesn't matter in our use case anyway. Also don't run the story watcher on the startup.

• #187 ebb1923 Thanks @tajo! - Fix story source escaping.

• #190 21959e9 Thanks @tajo! - Fix: Export default title and meta params. They were not correctly applied before. This might change the story IDs (URLs and the sidebar labels) if you were using them before.

Minor Changes

• #174 5abef5f Thanks @tajo! - - Add ladle preview command to quickly open a serve for the build folder.
  • Fix host and https options for serve and preview commands.
  • Measure time and size of the build. Display it.

Patch Changes

• #173 ddaebfd Thanks @GeorgeNagel! - Add engine settings and node restriction for @ladle/react so that install fails for users when node < 16.x

• #170 04714c9 Thanks @GeorgeNagel! - Enforce that Node version >= v16.0.0. This causes a loud failure when installing ladle with an old version of Node, as opposed to silently failing and causing difficult-to-diagnose bugs.

• #172 5049ce9 Thanks @tajo! - Fix Chrome (tab) re-opening for pnp environments..

Patch Changes

• #166 14a1619 Thanks @tajo! - Move React Context into a separate package so there is a single instance in the dev mode and useLadleContext hook works. Also, adding some documentation for the hook.

Patch Changes

• #166 14a1619 Thanks @tajo! - Move React Context into a separate package so there is a single instance in the dev mode and useLadleContext hook works. Also, adding some documentation for the hook.

• #166 14a1619 Thanks @tajo! - Align server.open more with the official Vite's API.

• Updated dependencies [14a1619]:

  • @ladle/[email protected]

Patch Changes

• #163 06d8a62 Thanks @tajo! - Set ellipsis to top level sidebar items.

Minor Changes

• #162 ff731f5 Thanks @kazuma1989! - Load vite.config.ts the same way as Vite

  WHAT the breaking change is

  (Only for the package maintainers) a new E2E packages is added.

  WHY the change was made

  Ladle was not able to handle vite.config.ts the way Vite does.
  For example, Ladle was not able to load vite.config.ts which imported other TS modules.

  HOW a consumer should update their code

  (Only for the package maintainers) recognize a new e2e workspace with pnpm install.

• #156 0e316d6 Thanks @tajo! - Reuse the same tab for Ladle serve when the env is Google Chrome and OSX.

Patch Changes

• #154 a53c25a Thanks @tajo! - Set default cacheDir to process.cwd() + node_modules/.vite

Major Changes

• #153 05bee5d Thanks @tajo! - - Ladle now loads top-level vite.config.js/ts/mjs and uses all its options.
  • All Vite related options from config.mjs removed and an error will be thrown, use vite.config.js instead.
  • enableFlow option removed, you can create your own plugin (check our e2e/flow test).
  • Programmatic API imports changed to @ladle/react/serve and @ladle/react/build.
  • --out renamed to --outDir to mimic Vite configuration, added -o alias, outDir moved to top-level in config.mjs.
  • --port has alias -p, port moved to top-level in config.mjs.
  • vite.config.js can be customized through viteConfig and --viteConfig.
  • --base-url removed, use base in vite.config.js.
  • --open removed, use server.open in vite.config.js.
  • --sourcemap removed, use build.sourcemap in vite.config.js.

Patch Changes

• #147 f9a4965 Thanks @tajo! - Add generic Axe check for (mostly) empty Ladle instance to make sure that projects running axe don't have a problem with Ladle.

Minor Changes

• #146 8568de6 Thanks @tajo! - Reload the page if there was a new story added or removed.

Patch Changes

• #144 daa717d Thanks @tajo! - Fixing sourcemaps when using ladle build --sourcemap while using virtual module for our story list and metadata.

Patch Changes

• #139 421a0c3 Thanks @tajo! - Force page reload for stories that are defined through .bind({}) syntax (controls). It seems that react-refresh can't detect those when creating boundaries.

Patch Changes

• #134 2351356 Thanks @tajo! - Stories with controls defined through ArgTypes only (and not args at the same time) caused runtime error

• #133 f0a42ad Thanks @tajo! - Add explicit types for children of GlobalProvider (required for React 18 compatibility)

• #137 515d069 Thanks @tajo! - Allow typescript typecast default export syntax when parsing stories.

• #135 c027c8c Thanks @tajo! - Surface all errors that happen during the story discovery (parsing) stage. Show them in the UI (a new landing page) and the CLI. Adds information how to deal with them as well.

• #136 fa8db60 Thanks @tajo! - Undo some basic CSS resets from normalize/preflight that impact Ladle's UI when used.

• #138 e2069f4 Thanks @tajo! - Add a section explaining the limitations of story syntax - some parts need to be static so they can be parsed.

• #126 0a44aa2 Thanks @beckend! - feat: allow configuration of the whole Vite config.resolve object

Minor Changes

• d40aa73: Changing the tooling to turborepo

Patch Changes

• 2c7263c: Remove conventional commits

• build: add husky hooks to check formatting and commit messages locally: We enforce conventional commits and prettier in the CI, this also adds pre-commit hooks so developers get the feedback early and locally.
• feat: add vite-tsconfig-paths plugin and allow add custom vite plugins: If you alias some of your imports and use TS/tsconfig, Ladle now includes these paths automatically.
• chore: update vite version
• feat: make flow types support opt-in: Ladle supported flow types by default; however, they bring some serious performance hit since esbuild can't process them without a JS plugin. The support is now optional and you have to opt-in through enableFlow: true.
• docs: improve no stories found landing page
• feat: add css.modules option into the config - You can now pass all the css.modules options to Vite

Related issues: #78, #76, #70, #66, #59