You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 26, 2018. It is now read-only.
Hi, I'm making an app which is targeted to modern browsers (which support ES2015 more than 90%), and basically I need babel only for modules support. So I use custom .babelrc, without preset and only with 1 plugin. This reduces resulting bundle and speeds up development.
Unfortunately, latest version of vueify throws errors: npm install --save-dev babel-preset-es2015 while parsing file: SomeComponent.vue. While this can be quite easily solved by installing said preset, I'd prefer not to clatter my package.json. Can this be solved somehow?
The text was updated successfully, but these errors were encountered:
@hogart I totally agree. Actually removing or commenting out these lines will get you building vue apps with only two dependencies (vue and vueify), which is kinda really nice.
Only then you need to use commonjs modules in <script> tags like so
I might be missing something out, because I only tried it on most trivial hello world example app, but I'd love to be able to use less dependencies too.
@yyx990803 what do you think? We still probably want to keep es2015 as default. I'm working on a solution where you'd say <script lang="noncompiled"> (or something like that) and be able to skip all babel stuff.
Hi, I'm making an app which is targeted to modern browsers (which support ES2015 more than 90%), and basically I need babel only for modules support. So I use custom .babelrc, without preset and only with 1 plugin. This reduces resulting bundle and speeds up development.
Unfortunately, latest version of vueify throws errors:
npm install --save-dev babel-preset-es2015 while parsing file: SomeComponent.vue
. While this can be quite easily solved by installing said preset, I'd prefer not to clatter my package.json. Can this be solved somehow?The text was updated successfully, but these errors were encountered: