Fresh install of decaffeinate is throwing a babel compile error
See original GitHub issuedecaffeinate is crashing on my CoffeeScript input:
language = "coffeescript"
I get this error:
Error: Plugin conflict between `["pipelineOperator", { proposal: "smart" }]` and `["recordAndtuple", { syntaxType: "hash"}]`.
Only getting this locally, not on the repl
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:11
Top Results From Across the Web
Error when compiling with babel - node.js - Stack Overflow
I found that the 'npm run build' will call 'babel src --out-dir lib' firstly in package. json. So this errors was throw by...
Read more >Bug Report - GitHub
Recently I'm trying to setup babel with webpack. and I'm getting an error. ERROR in ./src/index.js Module build failed (from ./node_modules/ย ...
Read more >Babel Users' Guide - LLNL Software Portal
Decaf demonstrates how Babel can be used to implement a component framework. ... with an error, but if the configuration works, the build...
Read more >sucrase - npm
Sucrase is an alternative to Babel that allows super-fast development builds. Instead of compiling a large range of JS features to be able...
Read more >Circular errors about babel-loader when trying to launch app
Remove "babel-loader" from dependencies and/or devDependencies in the package.json file in your project folder. Run npm install or yarn,ย ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Alright, I believe this is fixed now since decaffeinate depends on
@codemod/parser@^1.1.0
, which should pull in1.1.1
which I just published. If itโs still not working feel free to comment again.It seems likely this was broken by https://github.com/babel/babel/pull/13191, which means babel 7.15.x probably broke some assumptions made by
@codemod/parser
. Iโve reproduced the error there and will issue a fix.