Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Initialization error

See original GitHub issue

The plugin stopped working after I upgraded to Node 6.0. After updating Brunch to 2.7.4, it started throwing the following error:

$ LOGGY_STACKS=true brunch build --production
01 May 18:08:05 - error: Initialization error -  Cannot read property 'brunchPluginName' of null 
Type  at loadPackages.filter.arg (/Users/diogo/Code/juros/node_modules/brunch/lib/plugins.js:140:33)
  at Array.filter (native)
  at Object.exports.init (/Users/diogo/Code/juros/node_modules/brunch/lib/plugins.js:139:38)
  at BrunchWatcher.application.loadConfig.then.then.then.cfg (/Users/diogo/Code/juros/node_modules/brunch/lib/watch.js:110:19)

The error goes away when I remove sass-brunch from my package.json.

This is what I have in my brunch-config.coffee:

  plugins:
    sass:
      mode: 'native'
      options: includePaths: ['node_modules']

Issue Analytics

State:
Created 7 years ago
Comments:7

Top GitHub Comments

5reactions

jrautcommented, May 17, 2016

I had the same problem with brunch (2.7.7) which was installed globally. As in op, the error apperared for the first time after installing brunch-sass and disappeared when brunch-sass was removed from package.json.

This got fixed with the following procedures:

removed node_modules
switched node version with nvm install 6.1.0
reinstalled packages with npm install

4reactions

AdamTcommented, Dec 4, 2016

I got this error with node 7.2. However I’ve found that if I remove /node_modules and then run npm install again it works fine. No need to downgrade node version.