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.

Production build fails with "error: "version" is a required argument."

See original GitHub issue

Description

building for production fails

Expected behavior

building for production should finish

Actual behavior

After runing production build I get

18:30:29 - error: "version" is a required argument.
  at Object.getArg (/Users/uros/Sites/wandera/node_modules/source-map/lib/util.js:24:11)
  at SourceMapConsumer.BasicSourceMapConsumer (/Users/uros/Sites/wandera/node_modules/source-map/lib/source-map-consumer.js:288:22)
  at new SourceMapConsumer (/Users/uros/Sites/wandera/node_modules/source-map/lib/source-map-consumer.js:22:7)
  at prepareSourceMap (/Users/uros/Sites/wandera/node_modules/brunch/lib/fs_utils/generate.js:130:48)
  at processJob.then.optimized (/Users/uros/Sites/wandera/node_modules/brunch/lib/fs_utils/generate.js:151:17)
  at process._tickCallback (internal/process/next_tick.js:103:7)

Environment

Brunch: 2.10.8
Node.js: v6.7.0
NPM: 3.10.3
Operating system: osx

`package.json` contents

"devDependencies": {
    "autoprefixer": "^6.7.3",
    "brunch": "^2",
    "coffee-script-brunch": "^2",
    "coffeelint-brunch": "^2",
    "digest-brunch": "^1.4.0",
    "git-revision": "*",
    "groundskeeper-brunch": "0.0.4",
    "handlebars-brunch": "^2",
    "karma": "~0.13",
    "karma-chrome-launcher": "~0.1",
    "karma-coffee-preprocessor": "~0.2",
    "karma-coverage": "~1.1",
    "karma-firefox-launcher": "~0.1",
    "karma-junit-reporter": "~1.1",
    "karma-mocha": "~1.2",
    "karma-mocha-reporter": "~2.2",
    "karma-phantomjs-launcher": "~1.0",
    "karma-safari-launcher": "~0.1",
    "keyword-brunch": "^2",
    "mocha": "~3.1",
    "phantomjs-prebuilt": "~2.1",
    "postcss-brunch": "0.5",
    "sass-brunch": "^2",
    "uglify-js-brunch": "^2"
  },

Other useful files, when present (log, `bower.json` etc.)

Latest version I used was 2.8.x and no errors with the same codebase and configuration

Issue Analytics

State:
Created 7 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

shvaikaleshcommented, Mar 5, 2017

Try https://babeljs.io/docs/plugins/transform-remove-console. groundskeeper is so 2013.

0reactions

denysdovhancommented, Mar 5, 2017

@urosgruber babel-brunch with transform-remove-console plugin would be much more better solution:

module.exports = {
  plugins: {
    babel: {
      plugins: ['transform-remove-console']
    }
  }
}

Top Results From Across the Web

Error: "version" is a required argument · Issue #12229

I think I figured it out, the build process was crashing due to OOM errors and I'm assuming the source maps were being...

How to fix the webpack error "version" is a required ...

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not...

Error: "version" is a required argument

info "fsevents@1.2.13" is an optional dependency and failed compatibility check. Excluding it from installation. [3/4] Linking dependencies... [ ...

To v5 from v4

Make sure your build has no errors or warnings. There might be new errors or warnings because of the upgraded versions of webpack...

Common errors

Errors · Broken npm installation · Random errors · No compatible version found · Permissions errors · Error: ENOENT, stat 'C:\Users\<user>\AppData\Roaming\npm' on ...