“include in your project” means the files will be in the packaged tarball that is created when you run npm publish. You can also run npm pack to generate the tarball for inspection without actually triggering a publish. This way you can actually open the generated tarball and inspect which files were/were not included. While … Read more
The test command is the command that is run whenever you call npm test. This is important when integrating with continuous integration/continuous deployment tools (such as jenkins, codeship, teamcity). Example: – say you deploy a project to AWS or some other cloud hosting provider, – you can set up your infrastructure to automatically run npm … Read more
To specify by default a exact version, you can change your npm config with save-exact: npm config set save-exact true You can also specify the prepend version with a tilde with save-prefix. And, no you can’t force user to update to a minor or a patch version, NPM uses semver and it’s the recommend way … Read more
For yarn and npm, the default behavior is that they look up into the parent directories. I had an outdated and forgotten package.json in my home folder without a license field: ~/package.json When running yarn install within my project: ~/my-project/package.json yarn then also found the one in my home directory and reported the error for … Read more
npm allows only to do cd dir && command -args, which will also run on Windows. A change to use node‘s spawn functionality has been made in PR https://github.com/npm/npm/pull/10958, but was rejected, due to the above solution.
When you pass in files for compilation with tsc src/index.ts, your tsconfig.json is ignored. From the documentation: When input files are specified on the command line, tsconfig.json files are ignored. Your npm build script should just be tsc without passing any files.
What is Browserslist? Browserslist is a tool that allows specifying which browsers should be supported in your frontend app by specifying “queries” in a config file. It’s used by frameworks/libraries such as React, Angular and Vue, but it’s not limited to them. Why would we want it? During development we want to use the latest … Read more
eslint “**/*.js” to run on all js files in all the folders recursively (in the current folder) You can also do: AnyFolder/**/*.js And to ignore a folder: eslint “**/*.js” –ignore-pattern node_modules/ Know more at eslint/command-line-interface
In case you use .env file, let’s use grep or eval to get a value environment variable from the .env file. Updated start2 as @Paul suggested: “scripts”: { “start”: “NODE_ENV=$(grep NODE_ENV .env | cut -d ‘=’ -f2) some_script”, “start2”: “eval $(grep ‘^NODE_ENV’ .env) && some_script” }
Using –prefix worked for me: npm –prefix /path/to/project run build Where path/to/project is the directory where your package.json with build command defined.