Hello all,

This error occurred to me when trying to install npm modules with npm install. I tried with Yarn but the error was similar:

error Couldn't find package "..." on the "npm" registry.

The solution was into the .npmrc file.

Read more

Hello all,
This is mostly a reminder for me. When publishing a new version on your Openshift environment a npm install is run by default. However you can configure it to install only the modules under dependencies in your package.json file instead of installing both dependencies and devDependencies modules.

Read more

Hello everybody,

I wrote this article with a very specific title since it’s a common practice for different use cases. I thought a lot of people would find this answer while looking for a method to pass a NODE_ENV variable exposed in the npm script of the package.json directly to the code.

Read more

Hello all,

This error is generated by the fact that you just upgraded a your major Node.js version, which is good, and your node_modules need to be re-installed.

I suggest you to run in your terminal rm -rf node_modules && npm install to re-install all the dependencies.

Have a good day!

Hello all,

At first Webpack can give you an hard time but after that, it’s all sugar!

Imagine you need to include a JSON file used for configuration in your `example.js` file:

1. Install the loader module json-loader:

npm install json-loader --save-dev

2. Add the loader to your webpack.config.js file:

loaders: [
   { test: /\.json$/, loader: 'json' },
   // other loaders 
]

3. Add in your `example.js` file the following line:

import config from '../config.json';

…and your JSON is ready to be used in your code, already parsed into a sweet object.

Cool, isn’t it?

What Webpack does being the scenes is converting the JSON file into a JS module and adding it to your build result:

/* some-webpack-require-number */
/***/  function(module, exports) {
  module.exports = {
    // your json content
  }
}
var config = __webpack_require__(some-webpack-require-number);