Hello World With Browserify

 Browserify

BUNDLE UP YOUR FIRST MODULE

Browsers don't have the require method defined, but Node.js does. With Browserify you can write code that uses require in the same way that you would use it in Node.

Here is a tutorial on how to use Browserify on the command line to bundle up a simple file called main.js along with all of its dependencies:

main.js

var unique = require('uniq');

var data = [1, 2, 2, 3, 4, 5, 5, 5, 6];

console.log(unique(data));

Install the uniq module with npm:

npm install uniq

Now recursively bundle up all the required modules starting at main.js into a single file called bundle.js with the browserify command:

browserify main.js -o bundle.js

Browserify parses the AST for require() calls to traverse the entire dependency graph of your project.

Drop a single <script> tag into your html and you're done!

<script src="bundle.js"></script>

NPM ERR Code E401: Unable to authenticate, need: Bearer authorization

 node.js - NPM ERR Code E401: Unable to authenticate, need: Bearer authorization - Stack Overflow

This is what worked for me.

First, delete the .npmrc file in your Users folder. This folder:

C:\Users\[your user name]

Then run this command in your project folder that has an .npmrc file in it:

npx vsts-npm-auth -config .npmrc

registry = "https://registry.npmjs.com/"
always-auth = true

npm install from tfs feed (on build process) give error: Unable to authenticate

 https://stackoverflow.com/questions/56824651/npm-install-from-tfs-feed-on-build-process-give-error-unable-to-authenticate

Create a file .npmrc in your project folder and add the following

registry=Your URL
always-auth=true

In the command prompt run both of these commands

npm install -g vsts-npm-auth --registry https://registry.npmjs.com --always-auth false

vsts-npm-auth -config .npmrc




NVM + .nvmrc

If you are using NVM like this, which you likely should, then you can indicate the nodejs version required for given project in a git-tracked .nvmrc file:

echo v10.15.1 > .nvmrc

This does not take effect automatically on cd, which is sane: the user must then do a:

nvm use

and now that version of node will be used for the current shell.

You can list the versions of node that you have with:

nvm list

.nvmrc is documented at: https://github.com/creationix/nvm/tree/02997b0753f66c9790c6016ed022ed2072c22603#nvmrc

Tested with NVM 0.33.11.

`npm build` doesn't run the script named “build” in package.json

 Source: https://stackoverflow.com/questions/29939697/npm-build-doesnt-run-the-script-named-build-in-package-json

Unfortunately npm build is already an internal command, as described in the docs:

This is the plumbing command called by npm link and npm install. It should generally not be called directly.

Because that command already exists, it always shadows over your "build": "node build.js".

The fully-qualified way to run your own script is with run-script or its alias run:

$ npm run build

npm start and others are the short-hand way, but is only an option when an existing npm command doesn't shadow it, like npm build does.

---

For posterity (as others have mentioned) npm build is used by npm to build native C/C++ Node addons using node-gyp. It's not documented well because usually it happens automatically, but if you're interested the source code is here.

What's the difference between a tilde (~) and a caret (^) in a npm package.json file?

Source:https://michaelsoolee.com/npm-package-tilde-caret/


So if you see ~1.0.2 it means to install version 1.0.2 or the latest patch version such as 1.0.4. If you see ^1.0.2 it means to install version 1.0.2or the latest minor or patch version such as 1.1.0.

If you use npm to manage packages in your JavaScript application, you’re probably familiar with the package.json file.

{
  "devDependencies": {
    "ember-cli": "~2.14.0"
  }
}

The syntax is in JSON format where the key is the name of the package and the value is the version of the package to be used.

npm uses the package.json file to specify the version of a package that your app depends on.

The version number is in semver syntax which designates each section with different meaning. semver is broken into three sections separated by a dot.

major.minor.patch

1.0.2

Major, minor and patch represent the different releases of a package.

npm uses the tilde (~) and caret (^) to designate which patch and minor versions to use respectively.