Category "package.json"

Different node package versions in different branches of app in package.json?

The scenario: We have several similar but customized Node applications, all of which include our own common library/package which we include as a dependency in

Inherit or share package.json dependencies

We got couple of different projects that are using main dependencies like React and TypeScript packages. Each of those projects(maintained by different dev team

How do I fix a vulnerable npm package in my package-lock.json that isn't listed in the package.json?

Github is telling me that a dependency in my package-lock.json file is vulnerable and outdated. The problem is that if I do npm install or npm update, neither o

React Native TypeError: undefined is not an object (evaluating 'props.getItem')

When navigating to certain screens on my React Native app (using expo), I am getting the following error: TypeError: undefined is not an object (evaluating 'pro

proxy not working for react and node

I'm having issues with the proxy I set up. This is my root package.json file: "scripts": { "client": "cd client && yarn dev-server", "server"

Optional-chaining in Angular

I'm using optional chaining on an object which in turn gives this error after compiling the code For example const someObj = {pet_animals: {'dog', 'cat'}}; cons

npm equivalent of yarn install --check-files (or yarn check)

Update for 2020 This question originally referred to the yarn check command, but the docs state that this is deprecated in v1, and removed in v2, and yarn insta

Should I update my npm version or use the one node.js provides?

I have a project that uses node.js 14.16.0. Both me and my teammember use that version. I use npm 6.14.11 and my teammember uses npm 7.x.x. This results in the

Setting homepage in package.json doesn't set PUBLIC_URL on build

Following the docs here (Building for Relative Paths), so setting homepage field in package.json doesn't set PUBLIC_URL during the build. Expected behavior %P

What's the difference between dependencies, devDependencies and peerDependencies in npm package.json file?

This documentation answers my question very poorly. I didn't understand those explanations. Can someone say in simpler words? Maybe with examples if it's hard t

How to remove folder with npm before build

I've got a scripts "build": "rimraf dist webpack --progress --config webpack/prod.js", But actually,it removed not dist but all file inside webpack folder. But

Locked package.json files in Docker container using docker-compose

I'm using Docker for Mac and Docker Compose for development of a Node.js application and I'm experiencing an error with the package.json file being locked. The

What should I put in the license field of package.json if my code is only for use by the company I work for?

NPM 2.11.3 I'm building a library in Node. This library is only for use by the company I am currently working for. I think this means that the license is "None"

What should I put in the license field of package.json if my code is only for use by the company I work for?

NPM 2.11.3 I'm building a library in Node. This library is only for use by the company I am currently working for. I think this means that the license is "None"

Why (and How Can I FIx) ESLint import/no-extraneous-dependencies Failures on Installed Packages?

When I run ESLint I get the following errors: 1:13 error 'joi' should be listed in the project's dependencies. Run 'npm i -S joi' to add it import/no-

Unable to generate Cucumber HTML reports on failure

I have created a project framework using Typescript and Cucumber BDD approach. The executions within the project are working and the cucumber html reports are a

What exactly does "next" mean in package.json dependencies?

What exactly does next mean in package.json dependencies? "dependencies": { "react": "^15.4.2", "react-dom": "^15.4.2", "react-router-dom": "next" }

AngularFireFunctionsModule from AngularFire Causes build errors

I've run into a bit of a snag when adding in the AngularFireFunctionsModule. For some reason, despite having successfully included AngularFireModule, AngularFir

Error when deploying react app and it keeps sayings << Plugin "react" was conflicted between "package.json » eslint-config-react-app » >>

I have been having a little bit of issues when deploying my create react app, as it fails to compile and tells me Plugin "react" was conflicted between "package

Invalid options object. Dev Server has been initialized using an options object that does not match the API schema

I have been stock on this error on my project when I add "proxy": "http://localhost:6000" in my package.json. This is the error response after yarn start. Inva