npm-install

How do I pass npm parameters to dotnet publish?

社会主义新天地 提交于 2019-12-07 16:43:06
问题 Long story short, private npm registry, corporate network, can't download from github. I need to pass --no-optional to the npm install that dotnet publish executes as part of Target "PublishRunWebpack: (TargetId:162)" Any ideas? MSDN documentation @ https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-publish?tabs=netcore21 is super unhelpful. Using dotnet core 2.1, if it matters :) Thanks! 回答1: I swear, StackOverflow's greatest power is that the odds of figuring out your problem

npm install on laradock not working

半腔热情 提交于 2019-12-07 14:20:09
问题 I created a Laravel project using Laradock. When I run npm install I get the following output. > node-sass@4.9.0 install /var/www/npmtest/node_modules/node-sass > node scripts/install.js fs.js:119 throw err; ^ Error: EINVAL: invalid argument, open '/var/www/npmtest/node_modules/node-sass/package.json' at Object.openSync (fs.js:443:3) at Object.readFileSync (fs.js:348:35) at Object.Module._extensions..json (internal/modules/cjs/loader.js:719:20) at Module.load (internal/modules/cjs/loader.js

NPM - Cannot find name 'Many' and Cannot find namespace '_' from lodash library

百般思念 提交于 2019-12-07 12:37:03
问题 I'm trying to use lodash in my angular2 project. $ npm install --save lodash $ npm install --save @types/lodash I got this warning messages from installing lodash And this one for the types I ignored those warning messages and continue. Now in my component, I added this line.. import * as _ from 'lodash'; when the app starts to compile I get this errors in my console: ERROR in [default] /path/to/project/node_modules/@types/lodash/index.d.ts:244:12 Duplicate identifier '_'. ERROR in [default]

npm 3.x install fails on rename long paths in Windows/Azure

*爱你&永不变心* 提交于 2019-12-07 12:35:37
问题 npm 3.x install fails on rename long paths in Windows/Azure when deploying node.js due to long paths: npm ERR! EINVAL: invalid argument, rename 'D:\home\site\wwwroot\node_modules\azure_util\node_modules\pkgcloud\node_modules\gcloud\node_modules\gapitoken\node_modules\jws\node_modules\base64url\node_modules\meow\node_modules\indent-string\node_modules\repeating\node_modules\is-finite\node_modules\number-is-nan' -> 'D:\home\site\wwwroot\node_modules\number-is-nan' Is there away to overcome it

Npm install error EPERM Operation not permitted

為{幸葍}努か 提交于 2019-12-07 09:26:26
问题 So when trying to run the angular4 project today my first error was : npm install eperm operation not permitted so I thought to delete my node modules folder and retry. But running npm install I am running in to this error npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start" . I've closed vscode to try and run the install to make sure nothing was locking it. I've tried npm cache clean but results in errors. Todays latest

Docker compose v3 named volume & node_modules from npm install

*爱你&永不变心* 提交于 2019-12-07 04:14:15
问题 Using compose v3. In the build I copy package.json and run npm install into /var/www/project/node_modules I dont add any code in the build phase. In compose I add volumes - ./www:/var/www/project/www As everyone knows the host bind to /www will effectively "overwrite" the node_modules I installed during the build phase. Which is why we add a named module afterwards - ./www:/var/www/project/www - modules:/var/www/project/www/node_modules this works fine and dandy the first time we build/run

npm install: Is there a way to ignore a particular dependency in package.json

六眼飞鱼酱① 提交于 2019-12-07 02:11:48
问题 I am currently trying to create a docker container for a node.js project that contains a local dependency. This seems to cause an issue with docker so as a workaround I am trying to just copy the local dependency folders and just ignore their dependency entries in the package.json file. Is there a way to specify dependencies I would like to ignore and have npm install run and skip those enties? 回答1: That can be done using devDependencies The npm modules which you require only to develop, e.g.

npm install not compiling forked material-ui src into lib folder

谁都会走 提交于 2019-12-06 22:15:47
I am using material-ui in my app. I forked material ui and rolled back to pervious version and made some changes there, now I want to use the forked repo in my project so I used the following steps to install module from here : Go to fork's page Go to commits On the right side of the commit you want to use click Browse code On the browse code page right-click on Download ZIP button (or whatever it is that you are seeing) and copy . It should be something like this https://github.com/SoftwareMarbles/express-jsend/archive/fdd4089087d916fa6e3b5abaa1ff9dd9ea96df8d.zip Edit that URL replacing

Error installing vcremote on Mac OS X 10.11

北城以北 提交于 2019-12-06 20:56:31
I am trying to install vcremote with 'sudo npm install -g --unsafe-perm vcremote' but getting below error: /usr/local/bin/vcremote -> /usr/local/lib/node_modules/vcremote/bin/vcremote > thread-sleep@1.0.4 install /usr/local/lib/node_modules/vcremote/node_modules/thread-sleep > node-pre-gyp install --fallback-to-build node-pre-gyp ERR! UNCAUGHT EXCEPTION node-pre-gyp ERR! stack Error: Cannot find module 'internal/fs' node-pre-gyp ERR! stack at Function.Module._resolveFilename (module.js:472:15) node-pre-gyp ERR! stack at Function.Module._load (module.js:420:25) node-pre-gyp ERR! stack at Module

How to bundle dependencies in npm package?

大兔子大兔子 提交于 2019-12-06 16:22:25
I have a npm package which reference an other local package. It has a structure like so. deploy typescriptapp.tgz references mydependency package.json app.js app.css typescriptapp package.json webapp My typescriptapp package.json has the following dependencies "dependencies": { "mydependency": "file:../references/mydependency" }, My webapp package.json has the following dependencies "dependencies": { "typescriptapp": "file:../deploy/typescriptapp-1.0.0.tgz" }, When I use npm pack it work fine, but it is not included in the tarball. I also move the tarball to a deploy folder When I try npm