Replies: 3 comments 1 reply
-
As you pointed out, the main issue with |
Beta Was this translation helpful? Give feedback.
0 replies
-
Went with the concurrently package and merged in #149 |
Beta Was this translation helpful? Give feedback.
0 replies
-
I've checked the two checkboxes for you @bterone in the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Issue
Currently a newly generated project for running linting and fixes all execute synchronously ⬇️
However, there are libraries to run these commands in parallel and offer useful glob patterns like npm-run-all or concurrently 🤩
Solution
It's a good idea to integrate one of these libraries into our own template 🤗
Currently, on the project that we're working on, we use concurrently for linting, fixes, and tests
However, a newly generated Remix project will use npm-run-all and make use of different functionality like
run-p
for parallel running andrun-s
for sequential commands but that project hasn't seen any active development for 4 years now.It offers a much nicer developer experience to use either of these libraries and simplifies commands by a lot by cutting out the
npm run x && npm run y
chains that can appear when a project gets larger or has a lot of commands ✨Who Benefits?
Developers ❤️ and future template users 😳
What's next?
package.json
to be simplified, E.g.concurrently npm:lint:*
orrun-p lint:*
4 votes ·
Beta Was this translation helpful? Give feedback.
All reactions