Skip to content

Releases: tajo/ladle

@ladle/react@1.3.0

13 Jul 05:35
3230700

Choose a tag to compare

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 #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.

@ladle/react@1.2.0

24 Jun 20:55
b9f47f9

Choose a tag to compare

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..

@ladle/react@1.1.2

21 Jun 06:26

Choose a tag to compare

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/react-context@1.0.1

@ladle/react-context@1.0.1

21 Jun 06:26

Choose a tag to compare

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.

@ladle/react@1.1.1

14 Jun 20:21
c229fd3

Choose a tag to compare

Patch Changes

@ladle/react@1.1.0

12 Jun 20:14
dcfb5ba

Choose a tag to compare

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.

@ladle/react@1.0.1

10 Jun 00:01
a2e4ada

Choose a tag to compare

Patch Changes

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

@ladle/react@1.0.0

09 Jun 23:34
5ec00ba

Choose a tag to compare

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.

@ladle/react@0.16.0

25 May 21:22
52db7ee

Choose a tag to compare

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.

@ladle/react@0.15.2

24 May 20:20
2e06dc6

Choose a tag to compare

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.