Yeah, itβs how it works. I actually havenβt found value in the pinned-dependencies at all.
There are two options, you either treat shared as an actual package that should be developed separately. In this case, the solution will be to run rescript build -with-deps -w in the web and shared simultaneously.
Or instead of adding it as a dependency, you can set a path to shared in the bsconfigβs sources option. It has problems with artifact location and some other things, but it generally works.
After trying lerna, yarn, and pnpm workspaces earlier this year, we have also settled on pnpm. It gets weird sometimes with itβs lock file, but a fresh pnpm install fixes it easy
The workspace feature works pretty seamlessly, if you pnpm add something itβll just link your workspace version if you have one
I plan on introducing rescript into our monorepo soon. Do you mean you treat each package as its own package that has itβs own build step? And intellisense/module resolution is self contained right?
ReScript will not rebuild any pinned-dependencies in watch mode! This is due to the complexity of file watching, so youβd need to set up your own file-watcher process that runs rescript build on specific file changes.