I found that the following code fragment worked best for me. Since it uses require to load the package.json, it works regardless of the current working directory. var pjson = require(‘./package.json’); console.log(pjson.version); A warning, courtesy of @Pathogen: Doing this with Browserify has security implications. Be careful not to expose your package.json to the client, as … Read more
UPDATE: Alexander’s answer is the better solution and uses the same technique I describe here. I am leaving my answer in tact for posterity. The original point of my answer was to show that you can execute a small node script which should work on all platforms. In your preinstall script you can run a … Read more
In the module you are developing, add the conflicting packages to peerDependencies (and remove them from dependencies or devDependencies): // package.json “peerDependencies”: { “react”: “16.13.1”, “react-dom”: “16.13.1” }, Execute npm install in your module. Now add react and react-dom to the webpack configuration of your module as externals. These packages shouldnt be included in the … Read more
You can run individual script entries using npm run SCRIPTNAME: $ npm run postinstall
Login to your bitbucket account and under user settings add an app password: Add package dependency to your package.json as: “dependencies”: { “my-module”: “git+https://Xaqron:[email protected]/Xaqron/my-module.git#*” } Replace Xaqron with your own username and pwd with app password from step one. to install specific version add #v.v.v (i.e. #1.0.0) to the end of dependency URL.
In my experience, it does not make sense to put package-lock.json under version control. It makes managing large merge/rebases a nightmare. However, there are instances where the package-lock can be very useful. Recently (2017/10/10) moment.js introduced breaking changes in a minor version update. Meaning if one was to ship with no package-lock.json, and had something … Read more
https://developercommunity.visualstudio.com/t/support-json-schema-draft-06-draft-07/796216 VS still doesn’t support draft 7 for json-schemes and is stuck at draft 4-5. Hence the warning. It’s a false positive. EDIT Mike (see below) suggests a work around. Be sure to check it out and give Mike an upvote if it works (so that he’ll be the first answer listed).
You need to commit package.json. All other developers, after pulling the code, will just need to perform npm install to get the latest dependencies required for the project. Whenever you or someone else wants to add new dependencies to the project you perform npm install <dependencyName> or npm install –save-dev <dependencyName>. Then package.json is automatically … Read more
What worked for me was: commiting /dist to gh running npm install {username}/{repo}.git instead of manually adding the record to package.json