Fix module resolution issue

BrickworkSoftware · Sep 5, 2017 · e3a7033 · e3a7033
1 parent d23c7e2
commit e3a7033
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 3 deletions.
diff --git a/packages/react-scripts/config/paths.js b/packages/react-scripts/config/paths.js
@@ -66,6 +66,7 @@ module.exports = {
   appIndexJs: resolveApp('src/index.js'),
   asiagoPath: asiagoDirectory,
   asiagoNodeModules: asiagoNodeModules,
+  ownNodeModules: resolveOwn('../node_modules'),
   appPackageJson: resolveApp('package.json'),
   appSrc: resolveApp('src'),
   appPath: appDirectory,

diff --git a/packages/react-scripts/config/webpack.config.dev.js b/packages/react-scripts/config/webpack.config.dev.js
@@ -113,10 +113,11 @@ module.exports = {
     // if there are any conflicts. This matches Node resolution mechanism.
     // https://github.com/facebookincubator/create-react-app/issues/253
     modules: [
-      paths.appPath,
-      path.resolve(paths.asiagoPath),
-      paths.asiagoNodeModules,
       'node_modules',
+      paths.appNodeModules,
+      paths.asiagoNodeModules,
+      paths.appPath,
+      paths.asiagoPath,
     ].concat(
       // It is guaranteed to exist because we tweak it in `env.js`
       process.env.NODE_PATH.split(path.delimiter).filter(Boolean)