I am trying to migrate from NPM to Yarn for the sole reason of getting rid of 'node_modules' folder. I am trying to use CRA tool. However, on CRA it advises to
We have a CI/CD pipeline that executes yarn install. I want to execute DOWNLOAD=1 yarn install command without modifying the current pipeline. I'm wondering if
I have a CRA (create-react-app) and I updated npm. Following, npm run build started to fail with error: EACCES: permission denied, rmdir 'PATH/build/static/css
I'm trying to build a web app in AWS lambda and upload it to an S3 bucket. For that, I utilize child process, which is working fine locally. exec('cd /tmp/ &
I have a development environment file .env.development and a production .env file for my React web app. The .env.development has a value REACT_APP_NAME=My Test
Please tell me how to set up the preact-render-to-string on the express. https://github.com/preactjs/preact-render-to-string#render-jsx--preact--whatever-via-ex
I have installed node/npm using the nvm documentation. curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.29.0/install.sh | bash Then: nvm install
I'm trying to install dependencies in my project but when I run yarn install I get the following error [2/5] 🔍 Resolving packages... info There appears
We are facing critical vulnerability in minimist which is added as transitive dependency. +-- [email protected] | +-- [email protected] | | `-- [email protected]
Is it a way to update/generate package-lock.json without making real install of node_modules (like npm i)? I just need a valid package-lock.json based on my pac
I have cloned a repo from GitHub for a project. I've already installed node (-v 14.17.5) and npm (-v7.20.6), however when I run npm start I get the following co
I have cloned a repo from GitHub for a project. I've already installed node (-v 14.17.5) and npm (-v7.20.6), however when I run npm start I get the following co
I have a projectA that references a common package that my other Nodejs services will reference as well. The issue is how do I pack this up in a Docker file? Id
Recently I created organization in my account, for example 'my_org' so I can publish package under 'my_org' scope. But decided to create separate account (by or
I am running a node application on terminal. Have recently upgraded to node v8.5.0, but am getting this error: Error: The module '/tidee/tidee-au/packages/tide
I'm trying to use semantic-release to publish to a scoped private registry on gitlab but I keep getting error because it's trying to auth against the public reg
I've been getting the following warnings lately whenever I run any npm script: npm WARN npm npm does not support Node.js v12.4.0 npm WARN npm You should probab
Error in plugin "gulp-sass" Message: gulp-sass 5 does not have a default Sass compiler; please set one yourself. Both the sass and node-sass packages are permit
I'm using node v6.11.2, npm v5.3.0 and angular/cli v1.2.7. I'm suddenly receiving the following error message for a majority of my npm installs. Never seen it
I have a package.json file looks like this. "scripts": { "test": "echo \"Error: no test specified\" && exit 1", "start": "node src/app.js",