-
-
Notifications
You must be signed in to change notification settings - Fork 151
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
Separate index.js
and test.js
into different files
#234
Conversation
This looks good so far 👍 |
You can target Node.js 16. Here's what we may be able to take advantage of: Node.js 16
Node.js 14
|
I'll do this in a separate PR then, the diff for this one is already pretty large and I'd like the changes from the improvements to be easier to see. By the way, is this list posted anywhere else? It's a nice checklist for a project bumping their Node version. |
const parserOptions = buildParserOptions(parsedOptions); | ||
const result = buildResult(parsedOptions, parserOptions); | ||
|
||
process.title = result.pkg.bin ? Object.keys(result.pkg.bin)[0] : result.pkg.name; |
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.
Related to
added note to readme/
index.d.ts
about overridingoptions.pkg
this check doesn't take into account that, if options.pkg
was overridden, pkg.name
might not exist
It's just my personal list. I think the Node.js team may post something similar on new major versions. |
👍 |
I've split up associated tests from |
index.js
into different source filesindex.js
and test.js
into different files
Can you fix the merge conflict? |
Should be good now |
Per #233.
Tasks:
Add doc comments-> separate PRMiscellaneous fixes:
process.title
, added note to readme/index.d.ts
about overridingoptions.pkg
(needs better wording)