Skip to content
This repository has been archived by the owner on Apr 16, 2020. It is now read-only.

Warn about --type with shebang #37

Closed
wants to merge 12 commits into from
Closed

Conversation

jkrems
Copy link
Contributor

@jkrems jkrems commented Feb 16, 2019

Follow-up to #35

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

guybedford and others added 11 commits February 16, 2019 13:48
Refs: nodejs/modules#180

PR-URL: #6
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: John-David Dalton <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Refs: nodejs/modules#180

PR-URL: #6
Reviewed-By: Guy Bedford <[email protected]>
Reviewed-By: John-David Dalton <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Refs: nodejs/modules#180

PR-URL: #6
Reviewed-By: Guy Bedford <[email protected]>
Reviewed-By: John-David Dalton <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Refs: nodejs/modules#180

PR-URL: #6
Reviewed-By: Guy Bedford <[email protected]>
Reviewed-By: John-David Dalton <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
PR-URL: #6
Reviewed-By: Guy Bedford <[email protected]>
Reviewed-By: John-David Dalton <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
PR-URL: #6
Reviewed-By: Guy Bedford <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
@MylesBorins
Copy link
Contributor

@jkrems can you please rebase

@jkrems
Copy link
Contributor Author

jkrems commented Feb 16, 2019

Applied on top of latest lkgr.

@devsnek
Copy link
Member

devsnek commented Feb 16, 2019

i'd word this a little bit stronger. using arguments in hashbangs is something that should be avoided in general.

Works with stdin, `--eval`, `--print` as well as standard execution.
Works with stdin, `--eval`, `--print` as well as standard execution
when envoking `node` explicitly.
Does not work reliably when running via shebang (`#!/usr/bin/env node`)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should perhaps (like io.js provided both iojs and node binaries) node provide a node-esm or similar binary, so they can use that in the shebang instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I assume that'll be where it's heading. The question would be: Would this make a better general command / should it replace node as the "default" binary people would run?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only if they're invoking node on an extensionless ESM file - if the file has an extension, or if it's CJS, then node would still be preferred.

Since package.json bins can have extensions, this really only affects executable one-off ESM scripts, which won't be the majority (but are still an important use case)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, but if node-esm always works (after porting your code to ESM) and node works most of the time - why would you ever tempt fate and use node?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i wouldn't bet on another binary for this --mode option, given opposition to the design of the option, and the weight of an extra binary for very little configuration.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jkrems it wouldn't work on CJS files, and i'd expect it to throw if you tried to run with --type=esm on a file that had a non-esm file extension - the better question would be why would you tempt fate and use the alternative :-)

Copy link
Contributor

@guybedford guybedford Mar 7, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about something like:

Suggested change
Does not work reliably when running via shebang (`#!/usr/bin/env node`)
Note that this flag is not a reliable solution for shebang scripts (`#!/usr/bin/env node -m`) due to multiple arguments not being supported in POSIX environments.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it'd be anything that respects exec(3), so most POSIX platforms

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, updated to posix.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feel free to update the commit directly. This PR is just me suggesting a fix to an earlier PR, I don't have any personal attachment to the exact wording. :)

@nodejs-ci nodejs-ci force-pushed the modules-lkgr branch 2 times, most recently from 9301a06 to e721cd2 Compare March 14, 2019 08:10
@MylesBorins MylesBorins force-pushed the modules-lkgr branch 2 times, most recently from 484d1fb to 7efc53d Compare March 18, 2019 22:07
@nodejs-ci nodejs-ci force-pushed the modules-lkgr branch 3 times, most recently from c7fa700 to d69f765 Compare March 21, 2019 08:06
@MylesBorins MylesBorins force-pushed the modules-lkgr branch 5 times, most recently from 335d584 to 9a343ce Compare March 21, 2019 19:09
@nodejs-ci nodejs-ci force-pushed the modules-lkgr branch 3 times, most recently from 3a00b51 to bc101f6 Compare March 24, 2019 08:06
@MylesBorins MylesBorins force-pushed the modules-lkgr branch 3 times, most recently from fd5b55a to 3a40599 Compare March 27, 2019 02:42
@GeoffreyBooth
Copy link
Member

I think this is no longer relevant now that we no longer have a flag that applies to files?

@jkrems jkrems closed this Apr 18, 2019
@jkrems
Copy link
Contributor Author

jkrems commented Apr 18, 2019

Correct, closing! :)

@jkrems jkrems deleted the jk-mention-shebang branch April 18, 2019 16:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants