-
Notifications
You must be signed in to change notification settings - Fork 407
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
[Github Issue #554] improve dx #555
Conversation
"install:all": "npm i && cd packages/webapp && npm i && cd ../..", | ||
"ts-build": "./node_modules/typescript/bin/tsc -b --clean packages/server packages/cli && ./node_modules/typescript/bin/tsc -b tsconfig.build.json && ./packages/webapp/node_modules/typescript/bin/tsc -b packages/webapp/tsconfig.json", | ||
"ts-build": "tsc -b --clean packages/server packages/cli && tsc -b tsconfig.build.json && tsc -b packages/webapp/tsconfig.json", |
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.
That is going to use a global install of tsc, right? Is it better than using the repo one?
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.
Within the context of a npm script the executables in the node_modules/.bin
directory are added to the PATH
for execution so the repo tsc will be used here.
Reference: https://docs.npmjs.com/cli/v7/using-npm/scripts#path
Resolves #554
git add -A .
huskypre-commit
command so a dev can stage only certain files and isn't forced to stage all files every single timeproviders.yaml
file is very important and that file should be tightly maintained.tsx
files to be linted and adds--fix
option.env
file from source control to avoid accidental commits and use a.env.example
instead