npx resolve errors

[vvscode]

I have the error, so I added some debug info upfront:

console.log({
    npm_lifecycle_script: process.env.npm_lifecycle_script,
    _: process.env._,
    __filename
})

if (
    String(process.env.npm_lifecycle_script).slice(0, 8) !== 'resolve '
    && (
        !process.argv
        || process.argv.length < 2
        || (process.argv[1] !== __filename && fs.statSync(process.argv[1]).ino !== fs.statSync(__filename).ino)
        || (process.env._ && path.resolve(process.env._) !== __filename)
    )
) {
    console.error('Error: `resolve` must be run directly as an executable');
    process.exit(1);
}

that gives me:

{
  npm_lifecycle_script: 'resolve',
  _: '/Users/v.vanchuk/repo/test/node_modules/.bin/resolve',
  __filename: '/Users/v.vanchuk/repo/test/node_modules/resolve/bin/resolve'
}

I failed to follow the logic in this place

• when npm_lifecycle_script can have space at the end?
• why in general you make this restriction? (what's the purpose?)

Hope you can help / clarify this moment =)

Thanks in advance

[ljharb]

I'm a bit confused, can you clarify how you're getting this error?

[vvscode]

Sure =)

I just created new empty project

{
  "name": "resolve-demo",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "resolve": "^1.22.4"
  }
}

and installed dependencies with yarn

and inside I do run npx resolve

resolve-demo.zip

[ljharb]

aha, thanks :-) so, the bug is that it doesn't work with npx.

[vvscode]

I'm happy to help with the fix if you clarify the logic =)

shouldn't

String(process.env.npm_lifecycle_script).slice(0, 7) !== 'resolve'

or even

process.env.npm_lifecycle_script !== 'resolve'

solve the issue? (I didn't get that space at the end at all)

[ljharb]

There'll be no need for that workaround; i'll have a release cut momentarily.

[ljharb]

v1.22.5 is published.

[vvscode]

it works. Thanks

[vvscode]

@ljharb just for my understanding - is this limitation to have correct argv and have no errors on processing params?

[ljharb]

And to ensure it can’t be required/imported.

[vvscode]

function isEntryPoint() {
  return require.main === module;
}

might be more relyable solution for this

[ljharb]

require.main is deprecated and something that should never, ever have existed; i'm not going to use it.

[vvscode]

Can you link some information about it?
I checked node@20 docs and see it is there without any deprecation notes

https://nodejs.org/api/modules.html#accessing-the-main-module

[vvscode]

More than that

https://nodejs.org/api/deprecations.html#dep0138-processmainmodule

DEP0138: process.mainModule#

History

Version	Changes
v14.0.0	Documentation-only deprecation.

Type: Documentation-only

process.mainModule is a CommonJS-only feature while process global object is shared with non-CommonJS environment. Its use within ECMAScript modules is unsupported.

It is deprecated in favor of require.main, because it serves the same purpose and is only available on CommonJS environment.

DEP0138: process.mainModule[#](https://nodejs.org/api/deprecations.html#dep0138-processmainmodule) History Version Changes v14.0.0 Documentation-only deprecation.

Type: Documentation-only

process.mainModule is a CommonJS-only feature while process global object is shared with non-CommonJS environment. Its use within ECMAScript modules is unsupported.

It is deprecated in favor of require.main, because it serves the same purpose and is only available on CommonJS environment.

[vvscode]

@ljharb FYI^^

[ljharb]

I'm not going to use require.main ever, sorry. The current heuristic is my preferred approach.

[vvscode]

I proposed once, this mention was just to inform you about the state of that API. Thanks for helping me with the issues

Good luck