Closed Oluwasetemi closed 6 years ago
I'm shocked this didn't work. NPM allows variables using $npm_package_{A KEY IN PACKAGE.JSON}
and since main exist, it should work fine. But, I'll look into this tho.
Thanks for reporting.
@Oluwasetemi BTW, this happened after installing packages right?
Yes!!
Your dependencies properly didn't install completely
i should run it again? I am having issues with npm lately especially anytime i am setting for a large project
Yeah. Try running again. I'm not sure what your npm issues might be as I can't reproduce(I'm not using windows)
same error no such file or directory, open '$npm_package_main' $npm_package_main is an aliase right? for the main package in the node_modules
Not entirely. It's how variables in npm scripts are retrieved. Windows must have another way of resolving this. Lemme check.
It's different in windows. They use %npm_package_main%
. I'll have to write a fix for this later. Thanks for reporting :+1:
I might need a guide on how to start this open source contribution !! you are just in the flow of the fire๐ฅ
$npm_package_version - %npm_package_version% too right?
There you go! Install cross-var as devDependencies and follow the guide in the readme.
Awaiting a PR :grin:
That mean I have to leave it like it was before....then use cross-var to watch everything
Yeah
Because changing it to windows style will break it on linux.
Peace at last! I can now try to understand the project.. Thanks again.
sending a PR soon.
i ran
npm install
to set it up an got this error.using git-bash terminal, node v8.12.0 , npm v6.4.0