Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with Symlinks #214

Closed
ishortman opened this issue May 16, 2017 · 3 comments
Closed

Issues with Symlinks #214

ishortman opened this issue May 16, 2017 · 3 comments

Comments

@ishortman
Copy link

Description

Having issues with app project running inside a lerna project. The issue is a particular node module is replaced by a symlink and when adding the import statement the output returns a missing module inside node_modules. That module is a symlink within the lerna project and doesn't seem include the module during export. But when I run add the package such as yarn add the exported node_modules work. Is there settings or configuration to resolve symlinks?

Expected Behavior

Expected the symlinks to get resolved properly.

Observed Behavior

On the error I cleared out the cache and followed the recommended clearing of node cache.

Unable to resolve module `@test/test-redux` from `/projects/app/packages/app/App.js`: Module does not exist in the module map or in these directories: /projects/app/node_modules/@test

Environment

Ran this command to clear cache

watchman watch-del-all
rm -rf ./node_modules
npm cache clean
yarn cache clean
rm -rf $TMPDIR/react-*
yarn install
npm cache clean
yarn cache clean

Also specify:

  1. Mac OS
  2. iPhone Simulator & version: 10.2
@agrcrobles
Copy link

I am getting the following when using lerna Failed building JavaScript bundle any help is welcome

@anp
Copy link
Contributor

anp commented May 19, 2017

Related: facebook/react-native#637

@anp
Copy link
Contributor

anp commented May 22, 2017

I believe some work is happening upstream to improve symlink support for the RN packager, going to close this as this will be fixed once it is there. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants