Releases: tajo/ladle
@ladle/react@0.15.1
Patch Changes
-
#134
2351356Thanks @tajo! - Stories with controls defined through ArgTypes only (and not args at the same time) caused runtime error -
#133
f0a42adThanks @tajo! - Add explicit types for children of GlobalProvider (required for React 18 compatibility) -
#137
515d069Thanks @tajo! - Allow typescript typecast default export syntax when parsing stories. -
#135
c027c8cThanks @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
fa8db60Thanks @tajo! - Undo some basic CSS resets from normalize/preflight that impact Ladle's UI when used. -
#138
e2069f4Thanks @tajo! - Add a section explaining the limitations of story syntax - some parts need to be static so they can be parsed. -
#126
0a44aa2Thanks @beckend! - feat: allow configuration of the whole Vite config.resolve object
@ladle/react@0.15.0
Support tsconfig paths, css.modules and other improvements
- 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.modulesoptions to Vite