-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add package.json scripty options support for npm7 #94
Conversation
Looks good so far. Does npm7 document or guarantee that package_json_path will be absolute? |
@jasonkarns I'm not sure it's a guarantee, but the RFC says that |
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.
Just a single nitpick: typically prefer to camelCase function names, which necessitates lowercasing the N+1 chars of an initialism. so packageJson
instead of packageJSON
Do you also have a rationale for expanding the if
/elseif
into distinct if
conditionals? Functionally, they're the same; though "spiritually" they are a single if-elseif statement. If JavaScript had expression-valued-conditionals, ala ruby, it would be a single if-elseif by necessity.
Otherwise, I'm 👍 and appreciative!
Not really, it's just that with 4 |
Any news @jasonkarns? :) |
Is scripty still maintained ? This is quite of a blocker for people using npm 7 |
Closing because I think this is resolved in scripty 2.1.0 (via #105). Feel free to comment/reopen if this is not actually fixed! |
Closes #93