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.

(babel plugin) Error: [BABEL] .value is not a valid Plugin property

See original GitHub issue

I’m seeing this error when updating microbundle from 0.11 to 0.12


(babel plugin) Error: [BABEL] /home/circleci/project/src/resolver.ts: .value is not a valid Plugin property

Error: [BABEL] /home/circleci/project/src/resolver.ts: .value is not a valid Plugin property
    at Object.keys.forEach.key (/home/circleci/project/node_modules/@babel/core/lib/config/validation/plugins.js:52:56)
    at Array.forEach (<anonymous>)
    at validatePluginObject (/home/circleci/project/node_modules/@babel/core/lib/config/validation/plugins.js:50:20)
    at instantiatePlugin (/home/circleci/project/node_modules/@babel/core/lib/config/full.js:209:55)
    at cachedFunction (/home/circleci/project/node_modules/@babel/core/lib/config/caching.js:33:19)
    at loadPluginDescriptor (/home/circleci/project/node_modules/@babel/core/lib/config/full.js:200:10)
    at config.plugins.reduce (/home/circleci/project/node_modules/@babel/core/lib/config/full.js:69:20)
    at Array.reduce (<anonymous>)
    at recurseDescriptors (/home/circleci/project/node_modules/@babel/core/lib/config/full.js:67:38)
    at loadFullConfig (/home/circleci/project/node_modules/@babel/core/lib/config/full.js:108:6)

In case it helps, here’s the project where this error manifests: https://github.com/decentralized-identity/did-resolver/pull/31

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

mirceaniscommented, Jun 12, 2020

Progress report: I used yarn install --flat and forced @babel/core to a single version. It works now but it feels very hacky. I don’t know of a way to accomplish the same result with npm so this workaround doesn’t work for people that don’t want to switch to yarn

0reactions

developitcommented, Jun 17, 2020

@wardpeet I wonder if there’s something we’re doing wrong when massaging the configuration:

https://github.com/developit/microbundle/blob/afafa6d2138fdcbfcde5da0655f0b89fb06e7d5b/src/lib/babel-custom.js#L14-L37

Top Results From Across the Web

BABEL .default is not a valid Plugin property at Object.keys ...

otherwise Babel will not be able to process it properly when configured via a Webpack config. Share.

babel/plugin-proposal-class-properties

When true , class properties are compiled to use an assignment expression instead of Object.defineProperty . ⚠️ Consider migrating to the top level ......

babel/plugin-transform-modules-commonjs

When using exports with babel a non-enumerable __esModule property is exported. This property is then used to determine if the import is the...

Options - Babel.js

Babel's default return value includes code and map properties with the resulting generated code. In some contexts where multiple calls to Babel are...

Upgrade to Babel 7

Separation of the React and Flow presets ... babel-preset-react has always included the flow plugin. This has caused a lot of issues with...