`npx resolve` errors about resolve HOT 17 CLOSED

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

from resolve.

v1.22.5 is published.

from resolve.

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

from resolve.

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

from resolve.

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

from resolve.

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

from resolve.

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

from resolve.

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

from resolve.

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)

from resolve.

about workaround:

I added to package.json script

"scripts": {
       "resolve": "./node_modules/resolve/bin/resolve"
}

and run it with npm run resolve / yarn run resolve

just in case someone else faced the issue

from resolve.

it works. Thanks

from resolve.

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

from resolve.

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

might be more relyable solution for this

from resolve.

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

from resolve.

More than that

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

DEP0138: process.mainModule#

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.

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.

from resolve.

@ljharb FYI^^

from resolve.

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

from resolve.