Closed subhaze closed 8 years ago
Custom engines aren't supported in CodeKit 3. Gotta use the internal Babel version.
Sent from my iPhone
On Jun 13, 2016, at 12:01, Michael Russell notifications@github.com wrote:
Quick, short summary: Using a non-CodeKit babel produces an error
Babel: Transpiling failed:
Error: Cannot find module 'babel-preset-es2015-rollup' [...] I could be doing this wrong, but I assumed the plugin would be installed local to the current project. I'm using a source/ build/ setup. I thought at first it may not be looking in the source/ so added another node_modules in the root for the project still no dice.
Expected results: Understand how Custom Presets/Plugins work in CK for Babel
Actual results: Not quite sure how they work based on current information provided by UI.
Exact steps to reproduce: save `main.js A link to download a simplified project or file that shows the issue:
Your configuration (any details about your system that you think might be relevant)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
OK, so it reads installed via npm and kept up-to-date on your own, so the npm that comes with CK I assume. And I guess this means on production builds npm modules aren't touched unless provided by CK?
Neeeeevvvverrrrrrrrmind, was having a dumb moment.
Quick, short summary: Using a non-CodeKit babel preset produces an error
I could be doing this wrong, but I assumed the plugin would be installed local to the current project. I'm using a source/ build/ setup. I thought at first it may not be looking in the source/ so added another node_modules in the root for the project still no dice.
Expected results: Understand how Custom Presets/Plugins work in CK for Babel
Actual results: Not quite sure how they work based on current information provided by UI.
Exact steps to reproduce: save
main.js
in attached project.ck3_test3.zip
A link to download a simplified project or file that shows the issue:
Your configuration (any details about your system that you think might be relevant)