Closed YuryShkoda closed 3 years ago
Is anyone else aware of this issue?
@darcyclarke - is there a reason to remove the label? is this considered a nofix?
npm v6
is no longer in active development; We will continue to push security releases to v6
at our team's discretion as-per our Support Policy.
If your bug is preproducible on v7
, please re-file this issue using our new issue template.
If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo
Closing: This is an automated message.
Current Behavior:
If you install an older version of the package
npm i -g <package>
and after that install a newer version of itnpm i -g <package>@latest
, the latest source code will be downloaded, but the functionality will be used from older version. If you change any of the files located at/usr/local/lib/node_modules/<package>
, npm will pick up the right source code.Expected Behavior:
The right source code should be used after installing a newer version.
Steps To Reproduce:
npm i -g @sasjs/cli@1.12.0
sasjs -v
- to get the version of this packagesasjs folder create
sasjs help
for a full list of available commands.'npm i -g @sasjs/cli@latest
sasjs -v
- to get the version of this packagesasjs folder create
sasjs help
for a full list of available commands.'cd /usr/local/lib/node_modules
rm -rf @sasjs
npm i -g @sasjs/cli@latest
sasjs folder create
Target name wasn't provided. Using 1 by default.
Environment: