feat: use NODE_PATH for root directory(fix #396)

[yaodingyd]

Description

Add a babel plugin to use NODE_PATH for root

Review

• Check the copy
• ...
• ...

Pre-merge checklist

• ...
• ...

Screenshots

Before	After
Image	Image

[pedronauck]

Sorry dude, but I don't think that this is the best strategy for NODE_PATH. You can simply put the resolved NODE_PATH on the resolve.modules on webpack instead of using some new babel plugin.

[yaodingyd]

@pedronauck like the updated?

[pedronauck]

you need to set some additional code:

1. change populateNodePath on this file to:

const populateNodePath = () => {
  // We support resolving modules according to `NODE_PATH`.
  // It works similar to `NODE_PATH` in Node itself:
  // https://nodejs.org/api/modules.html#modules_loading_from_the_global_folders
  // Note that unlike in Node, only *relative* paths from `NODE_PATH` are honored.
  // Otherwise, we risk importing Node.js core modules into an app instead of Webpack shims.
  // https://github.com/facebook/create-react-app/issues/1023#issuecomment-265344421
  // We also resolve them to make sure all tools using them work consistently.
  envDotProp.set(
    'node.path',
    envDotProp
      .get('node.path', '')
      .split(path.delimiter)
      .filter((folder: any) => folder && !path.isAbsolute(folder))
      .map((folder: any) => path.resolve(root, folder))
      .join(path.delimiter)
  )
}

2. then set resolve.modules like that:

config.resolve.modules
    // prioritize our own
    .add(paths.ownNodeModules)
    .add(paths.appNodeModules)
    .add('node_modules')
    .add(srcPath)
    .add(paths.root)
    .merge([
      envDotProp
        .get('node.path')
        .split(path.delimiter)
        .filter(Boolean),
    ])

And don't forget to submit your pull request on IssueHunt
https://issuehunt.io/repos/125596489/issues/396

[yaodingyd]

@pedronauck thanks! updated

[pedronauck]

thanks dude 🙏

[yaodingyd]

thank you!