Microbundle: Failing build: (terser plugin) Error: `sourcemap`

Created on 2 Sep 2019  Â·  3Comments  Â·  Source: developit/microbundle

// package.json
{
  "name": "mb",
  "version": "1.0.0",
  "description": "",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "source": "index.js",
  "main": "dist/index.js",
  "devDependencies": {
    "microbundle": "^0.11.0"
  }
}
// index.js
export const test = () => console.log('test')
â–¶ microbundle         
node-resolve: setting options.module is deprecated, please override options.mainFields instead
node-resolve: setting options.jsnext is deprecated, please override options.mainFields instead
node-resolve: setting options.module is deprecated, please override options.mainFields instead
node-resolve: setting options.jsnext is deprecated, please override options.mainFields instead
node-resolve: setting options.module is deprecated, please override options.mainFields instead
node-resolve: setting options.jsnext is deprecated, please override options.mainFields instead
    `sourcemap` is not a supported option

(terser plugin) Error: `sourcemap` is not a supported option
DefaultsError: `sourcemap` is not a supported option
    at a.get (/home/sergey/Sandbox/microbundle/node_modules/terser/dist/bundle.min.js:1:525)
    at reportError (/home/sergey/Sandbox/microbundle/node_modules/jest-worker/build/child.js:75:11)
    at execMethod (/home/sergey/Sandbox/microbundle/node_modules/jest-worker/build/child.js:93:5)
    at process.on (/home/sergey/Sandbox/microbundle/node_modules/jest-worker/build/child.js:40:7)
    at emitTwo (events.js:126:13)
    at process.emit (events.js:214:7)
    at emit (internal/child_process.js:762:12)
    at _combinedTickCallback (internal/process/next_tick.js:142:11)
    at process._tickCallback (internal/process/next_tick.js:181:9)

Most helpful comment

I had the same issue with 0.11.0, then I upgraded to the latest release 0.12.0-next.6 - it seems to work there.

All 3 comments

Getting same error

same

I had the same issue with 0.11.0, then I upgraded to the latest release 0.12.0-next.6 - it seems to work there.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jlkiri picture jlkiri  Â·  4Comments

retyui picture retyui  Â·  4Comments

yaymukund picture yaymukund  Â·  4Comments

Kikobeats picture Kikobeats  Â·  4Comments

sptimer picture sptimer  Â·  4Comments