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
Maybe a better title for this issue might be, exec() assumes the shelljs script is being run from the package root directory.
It would be awesome if exec(), or a new function that works similarly, would look in ancestor directories until it finds a package.json, and only then look for the package to execute in a node_modules subdirectory.
If exec() is run with the cwd being a subdirectory of the package, the function will silently fall back to the global installation of the package.
The text was updated successfully, but these errors were encountered:
Maybe a better title for this issue might be, exec() assumes the shelljs script is being run from the package root directory.
It would be awesome if exec(), or a new function that works similarly, would look in ancestor directories until it finds a package.json, and only then look for the package to execute in a node_modules subdirectory.
If exec() is run with the cwd being a subdirectory of the package, the function will silently fall back to the global installation of the package.
The text was updated successfully, but these errors were encountered: