-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Improve the package.json scripts #402
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
Conversation
|
Overall, this is a great addition 👍 , just two comments:
|
| /.idea/ | ||
| .env | ||
| build/ | ||
| .vscode/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious what you're ignoring here, did an extension or something change some workspace settings?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm using VS code scripts while developing, which are saved in .vscode, so since Xterm.js is used in VS code, I felt that's Ok to keep this here 😇
I can definitely remove this if you believe it's not needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's leave this here, since vscode might be creating any files, I think it's a good idea to ignore them for sure.
Non-blocking question: Should we change this to /.vscode/ like the /.idea/ above or not?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akalipetis thanks, I was mainly just wondering if an extension was being naughty 😛
.vscode can only appear at the root of the repo so .vscode/ should be fine.
dd95afa to
c048131
Compare
parisk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀 .
It just needs to resolve the conflict in package.json before merging 🙂 .
1. Include a `prestart` script, which runs the build 2. Make the `start` script just start the demo server 3. Add a new `dev` script, which contains the nodemon logic 4. nodemon now watches for changes in `*.ts` files and runs the start command Signed-off-by: Antonis Kalipetis <[email protected]>
Also, update the Procfile.dev with the updated `npm run dev` command. Signed-off-by: Antonis Kalipetis <[email protected]>
c048131 to
f00ea4b
Compare
prestartscript, which runs the buildstartscript just start the demo serverdevscript, which contains the nodemon logic*.tsfiles and runs the start commandThis allows for easier development, while also makes the different scripts we use simpler and self-contained.