-
Notifications
You must be signed in to change notification settings - Fork 0
chore: define build & package scripts #15
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
Auto-loads the correct Node version for many different version managers
We use a dedicated tsconfig file that only selects the files we need for the package.
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
5be39d2
to
0cf2c80
Compare
Tested package with yalc
0cf2c80
to
1b9786a
Compare
package.json
Outdated
"engines": { | ||
"node": ">=20.9.0", | ||
"yarn": ">=4.0.2" | ||
}, | ||
"scripts": { | ||
"tsc": "tsc", | ||
"prepublish": "tsc", |
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 believe we should also make sure all tests are passing and style is correct, thoughts @tuxmachine ?
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 agree, but that can be enforced in CI right? This is just ensuring that whenever we publish a package, we build a fresh package, and don't accidentally upload an outdated libs
folder.
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.
As of npm@5, prepublish
scripts are deprecated. Use prepare
for build steps and prepublishOnly
for upload-only.
prepublish is deprecated Co-authored-by: Tolga Paksoy <[email protected]>
2947035
to
b421622
Compare
Todo: