-
Notifications
You must be signed in to change notification settings - Fork 333
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Typescript! #888
Typescript! #888
Conversation
raineorshine
commented
May 2, 2021
•
edited
Loading
edited
- tsconfig
- source maps
- typescript-eslint
- mocha integration
- Split out getPeerDependencies
- Split out version manager functions
- Split out index functions
- Convert npm to typescript
- Convert yarn to typescript
- Remove module.exports syntax
- Remove vm from public API
- Branded version types (optional)
- Version, VersionRaw, VersionSpec
- Also Github urls, npm urls, etc
- Convert tests to typescript (optional)
- A lot of tests!!! Can be done incrementally
@XhmikosR Do you have experience with Typescript? Would love to have someone else check over my setup. I haven't gotten very far with the actual conversion but it's compiling and tests are passing at least. |
@@ -30,21 +30,23 @@ | |||
"raine" | |||
] | |||
}, | |||
"main": "./lib", | |||
"main": "./build/src", | |||
"scripts": { | |||
"build": "node scripts/build.js", | |||
"lint": "cross-env FORCE_COLOR=1 npm-run-all --parallel --aggregate-output lint:*", |
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.
Unrelated but forgot to mention this the other day: why do we have FORCE_COLOR=1
here? If it's for CI, this is now fixed there and locally it shouldn't be needed. It's one less devDependency :)
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.
It's not just for CI. npm-run-all
appears to have some known limitations with coloring. If I remove FORCE_COLOR=1
and run it locally it loses color output.
I'm not familiar with TypeScript either just a couple of quick thoughts:
|
Yup, I still need to do that. I have a
Good call. I just switched to "es2018" which targets node v10 (and soon can bump to "es2019" when we remove v10 support). |
43d3091
to
4acd967
Compare
a60b8f9
to
c21da2c
Compare
prompts ^2.4.1 → ^2.4.2 eslint-plugin-import ^2.24.2 → ^2.25.2 eslint-plugin-jsdoc ^36.0.8 → ^36.1.1 markdownlint-cli ^0.28.1 → ^0.29.0 yarn ^1.22.11 → ^1.22.17
Move to /src/lib: getCurrentDependencies, getInstalledPackages, upgradePackageData
@types/lodash ^4.14.168 → ^4.14.170 @types/node ^15.0.1 → ^15.6.1 @types/prompts ^2.0.11 → ^2.0.12 @types/semver ^7.3.5 → ^7.3.6 @typescript-eslint/eslint-plugin ^4.22.1 → ^4.25.0 @typescript-eslint/parser ^4.22.1 → ^4.25.0 eslint ^7.26.0 → ^7.27.0 eslint-config-standard ^16.0.2 → ^16.0.3 eslint-plugin-import ^2.23.0 → ^2.23.3 eslint-plugin-jsdoc ^34.2.2 → ^35.0.0 ts-node ^9.1.1 → ^10.0.0 typescript ^4.2.4 → ^4.3.2
…g license fields.
c21da2c
to
119206a
Compare