-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parcel should run script differently with different targets #935
Comments
Here is another idea (maybe it's a little too radical, but I like it) - what do you think about creating several separate projects, one for every target (like |
That is definitely way too radical (at the moment), however in the future it might be nice. |
Really hope this will happen.I use ts for server side code, with parcel -t node,this is simple, but I also need to run a nodemon process,feel wired. |
🙋 feature request
🤔 Expected Behavior
When user runs something like
parcel src/scripts/server.js -t node -d dist/server -o index.js
,parcel
should runnode dist/server/index.js
ornodemon dist/server/index.js
.Same thing goes for
electron
. It'll be great to have two separate targetselectron-main
andelectron-renderer
(like inwebpack
), first one should runelectron path/to/file.js dev
or something like that and the second one should do what--target=electron
is doing now.😯 Current Behavior
parcel
is always launching the same server as with--target=browser
option, which in my opinion makes no sense.🔦 Context
I'm developing an app which consist of three parts:
All three of this parts have shared codebase and I'd love to have three scripts in my
package.json
for each of them (or even two if there is a way to runparcel
middleware from main electron process)🌍 Your Environment
The text was updated successfully, but these errors were encountered: