When running MSBuld prior to setting up my NPM install task, I get an error that the files that NPM would install are missing. The line number of the error is from a file named \sproj. VSCode can not find the file when clicking on it and I don't have a file by that name in my project. What is this file?
Related
I recently created a simple npm package that provides blue button. After publishing it to npm. I install it to my another project but it is showing warning as shown in screenshot below.
I tried to use my own created npm package. But it is showing warning as "Could not find a declaration file for module 'blue-button-by-ayush'"
Every time when I install any npm package, it creates a folder called 'tmpnodejsnpm-cache'. See the picture below.
Why does this happen?
The unwanted generated folder
I'm new to NPM, but just downloaded it with NodeJS on Windows 10. I wanted Node JS to default to a path on OneDrive rather than constantly having to go there on the command prompt, so put this into my %PATH% variable.
However, I must have inadvertently changed something in the config of NPM, as now when I type NPM or any valid command (ie NPM init) - I get the following error:
Error: EINVAL: invalid argument, mkdir 'c:\users\RossCatley\Users\OneDrive - The Orthello Partnership\Website\Sandpit"'
It seems its trying to create the directory, and because I put it quotes originally because of the spaces in the directory name, its appearing as an invalid name with an end double quote (but not an opening double quote) when the mkdir is being run.
I've removed it from the PATH variable, uninstalled and reinstalled NPM, restarted the machine, but it still appears. I've looked for the .NPMRC file, but the only one I can find is empty, so I don't know where NPM is picking up the config to tell it to try to create this directory.
Can anyone enlighten me please?
Found it eventually, it was hidden in the .npmrc file in the directory of the project rather than the .npmrc file in /Appdata/roaming/npm. There is a prefix = "[directory]" directive which was causing the problem.
In a React Boilerplate project, I am trying to use a local module, but getting:
ERROR in ./node_modules/react-sortable-tree-theme-file-explorer/dist/main.js
Module build failed: Error: ENOENT: no such file or directory, open '/Users/username/Documents/project/node_modules/react-sortable-tree-theme-file-explorer/dist/main.js'
Both paths do exist:
$ ls node_modules/react-sortable-tree-theme-file-explorer/dist/main.js
node_modules/react-sortable-tree-theme-file-explorer/dist/main.js
and
$ ls /Users/username/Documents/project/node_modules/react-sortable-tree-theme-file-explorer/dist/main.js
/Users/username/Documents/project/node_modules/react-sortable-tree-theme-file-explorer/dist/main.js
...so I can't figure out what the complaint is. The paths and files DO EXIST. I used npm link initially, but that never worked, and so I also tried npm install ../react-sortable-tree-theme-file-explorer but it gives the exact same results.
I am importing the package as in:
import FileExplorerThemeBase from "react-sortable-tree-theme-file-explorer";
I am trying to set up an file watcher for .less files, but it isn't working.
I have globally installed less via npm (npm install -g less). And after this I set up the file watcher according to this documentation from JetBrains supprt. Here is a picture of the settings:
Everytime I will change my .less files, it will produce the following error:
/usr/local/lib/node_modules/less/bin/lessc --no-color styles.less
lessc: ENOENT: no such file or directory, open '/Applications/PhpStorm.app/Contents/bin/styles.less'
Process finished with exit code 1
What went wrong? Any suggestions?
Using the less compiler directly in the project folder via the command line works perfectly (e.g. $ lessc styles.less styles.css)
Using the less compiler directly in the project folder via the command -- line works perfectly (e.g. $ lessc styles.less styles.css)
Try doing the same then -- please try with $FileDir$ in the "Working Directory" field.