In a development environment, I'm wondering what the recommended approach is to confirm that yarn dependencies are fully up to date? I notice esbuild will happily build when the dependencies installed are out of date compared to the versions defined in package.json and it's not very obvious a yarn install needs to be run.
The standard seems to be a Procfile containing
js: yarn build --watch
The best I can come up with is using immutable-cache to try and make it throw an error., although it's still not obvious what's gone wrong.
dhh
commented
1 year ago
In a development environment, I'm wondering what the recommended approach is to confirm that yarn dependencies are fully up to date? I notice
esbuildwill happily build when the dependencies installed are out of date compared to the versions defined inpackage.jsonand it's not very obvious ayarn installneeds to be run.The standard seems to be a Procfile containing
The best I can come up with is using
immutable-cacheto try and make it throw an error., although it's still not obvious what's gone wrong.I just wanted to check I've not missed something obvious.