4 ms·
Jetbrains will automatically warn you if your package.json is ever out of sync with the actual installed packages (a little dialog pops up). It's not clear to m
by solardev 2y ago
Jetbrains will automatically warn you if your package.json is ever out of sync with the actual installed packages (a little dialog pops up). It's not clear to me how VScode handles this (and in fact, one of my colleagues often struggled with this). Closed issue with unclear resolution: https://github.com/microsoft/vscode/issues/66288 https://github.com/microsoft/vscode/issues/66288
It's one of the many, many, many nice little touches that Jetbrains offers over VScode, and I heavily recommend people who have never tried it to give it a shot for a few weeks/months. It's a LOT better than vanilla VSCode, and slightly better than VSCode + a ton of third-party extensions.
--------
Beyond that, I also see npm script chaining. e.g. instead of `npm run dev` to start your server, `npm run pre-dev-scripts` which call a bunch of other updates, style token generations, npm install, whatever. Combine that with git hooks (like pre-commit linting & formatting) and it's often pretty automatic. For external services, you should be able to specify them in some IDE config file that can trigger task runners, monitors, etc. and share that in the repo with your teammates: https://code.visualstudio.com/docs/editor/tasks https://code.visualstudio.com/docs/editor/tasks
That's a bit harder if you work across IDEs (like VScode and Jetbrains), but not always impossible. Our Docker auto-updates in VScode, for example, but doesn't do anything in Jetbrains :(
- gregoriol 2y agoThanks for your inputs: indeed jetbrains' tools can be helpful in a lot of ways! But this doesn't handle the database migrations, clearing caches nor any configuration change that should be updated with ansible though; maybe some plugins do but that would become too heavy to setup I was thinking of a tool like database migrations; so when you run the tool, it says "last time you ran me you were at revision x, now you are at revision x+3 so we will run A, B and C commands for you to get up to date", and a dev that works on something that would require a command to be run would have to write in into some migration file