You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
tns livesync ios
fails when one of the dependency has executables created innode_modules/.bin
directory.Some of npm packages may have executables, that are created in
node_modules/.bin
directory after callingnpm install
. These executables are used for calling the module directly, not via require. For example such module ismkdirp
. You can use it in code, but you can also call it directly fromnode_modules/.bin/mkdirp
.When we have such module as dependency, CLI is unable to process the resources when
tns livesync ios
ortns 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
tns create myApp
cd myApp
tns plugin add [email protected]
tns livesync ios --justlaunch
tns livesync ios
The last call will fail with EEXIST error.
The text was updated successfully, but these errors were encountered: