Error "ENOENT: no such file or directory, open '../../is-core-module/core.json"

[SuperOleg39]

Hello @ljharb!

Have this error in last resolve package version - ENOENT: no such file or directory, open '../../is-core-module/core.json

This change is breaking change for bundlers - 122bb64, because bundler can't process this require anymore.

Our case - we using webpack for server code (SSR application)

May I ask you to revert this change?

[ljharb]

The core.js import is deprecated; you should be using is-core-module directly. That said, I’ll see what i can do.

[SuperOleg39]

Hmm looks like 7c26483 has never been published?

[SuperOleg39]

var async = require('./lib/async');
async.core = require('./lib/core');
async.isCore = require('./lib/is-core');
async.sync = require('./lib/sync');

module.exports = async;

It is code from library entry point (latest published version), webpack trying to process all imports here

[ljharb]

yeah, good call.

7c26483 is part of the v2 prerelease; v1 is managed on a separate branch.

[ljharb]

tbh tho I'm surprised webpack wouldn't be able to see the fs.readFileSync call and inline the file's contents.

[oksankaa]

We have the same issue and we also use webpack.

[ljharb]

@oksankaa you're also bundling on the server?

[SuperOleg39]

tbh tho I'm surprised webpack wouldn't be able to see the fs.readFileSync call and inline the file's contents.

It is quite impossible)
Popular bundlers have support for import/require with dynamic paths, but it is very limited by bunch of reasons

[oksankaa]

@oksankaa you're also bundling on the server?

yes

[foolzhang]

[JKapitein]

For us it's generating the following in webpack:

var data = JSON.parse(String(fs.readFileSync(path.join(path.dirname(/*require.resolve*/(91928)), 'core.json'))));

This obviously breaks because dirname won't take a number argument.

[trentm]

@ljharb Do you intend to keep resolve@1.x using var data = require('./core.json');? (I'm inferring that was the intent, at least for the short term, by the "latest" dist-tag having moved to '1.22.2'.)

I'm currently maintaining require-in-the-middle and will try to get it to work with bundlers. I haven't looked at the resolve@2.x pre-releases yet.