In the @babel/core, config a String plugins, can not resolve module

[qingxiao]

Feature Request

babel/packages/babel-core/src/config/files/plugins.js

Line 99 in 731182e

return resolve.sync(standardizedName, { basedir: dirname });

this code use resolve.sync to load a plugin, when i config a plugin like that

{
    presets: ['@babel/preset-env']
}

Because the default here is { basedir: dirname }, so module will find by

0:"/Users/username/projectDir/node_modules"
1:"/Users/username/node_modules"
2:"/Users/node_modules"
3:"/node_modules"

resoleve module support resolve. sync (name, {paths: custormPaths}),
it can be added in thebable-loaderconfiguration? like webpack resolve loader config

...
    // in resolve/lib/node-modules-paths.js nodeModulesPaths 
    return opts && opts.paths ? dirs.concat(opts.paths) : dirs;
...

so we can use custorm path to find a module, Thanks!

[babel-bot]

Hey @qingxiao! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.

[nicolo-ribaudo]

You could use require directly in your Babel config.

[loganfsmyth]

Babels config system is not configurable. I'd use a jobJS config to return an absolute path if you need custom resolve logic.

[qingxiao]

Babels config system is not configurable. I'd use a job config to return an absolute path if you need custom resolve logic.

Ok, got it. thank you

[loganfsmyth]

Oh autocomplete screwed that up FYI, I meant "a js config".