Skip to content

Livesync ios is not working when dependency has executable #1571

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

Closed
rosen-vladimirov opened this issue Mar 7, 2016 · 1 comment
Closed
Labels
Milestone

Comments

@rosen-vladimirov
Copy link
Contributor

tns livesync ios fails when one of the dependency has executables created in node_modules/.bin directory.

Some of npm packages may have executables, that are created in node_modules/.bin directory after calling npm install. These executables are used for calling the module directly, not via require. For example such module is mkdirp. You can use it in code, but you can also call it directly from node_modules/.bin/mkdirp.
When we have such module as dependency, CLI is unable to process the resources when tns livesync ios or tns test ios is called. The calls pass only the first time, every consecutive call is failing.
CLI should not try copying any .bin directory to platforms dir - it has no valid point to have these executables on device.

Steps to reproduce

  1. tns create myApp
  2. cd myApp
  3. tns plugin add [email protected]
  4. tns livesync ios --justlaunch
  5. tns livesync ios
    The last call will fail with EEXIST error.
@pkoleva pkoleva added this to the 2.1 milestone Jun 7, 2016
@pkoleva
Copy link
Contributor

pkoleva commented Jun 7, 2016

Not reproduced in {N} 2.0.1

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

No branches or pull requests

3 participants