True, you have to rebuild the library to see the changes in the example. Most of the time, it's not an issue because you use the storybook (with a devserver) while you do intensive developments in the library.
However, if you want to rebuild automatically the library, I suggest to check out this tool: nodemon.io/
With this project structure i have to run build every time that i have a change in my library no? how can i solve that
True, you have to rebuild the library to see the changes in the example. Most of the time, it's not an issue because you use the storybook (with a devserver) while you do intensive developments in the library.
However, if you want to rebuild automatically the library, I suggest to check out this tool: nodemon.io/
You can just
npm run build:vite -- --watchThanks :)
this will not update the d.ts file so linked packages won't have any updated types. any solution around this that is not nodemon? @bastianw
You could use something like concurrently. You can run both watch commands in parallel.
Thanks for sharing. I've discovered recently a similar tool npm-run-all