My team and I ran into a production issue where we were not passing the results of vue-svg-loader to babel-loader. This caused a production issue with IE11. After reading the documentation a bit more carefully, it looks like babel-loader is implicitly used throughout to docs.
Would there be a benefit to adding a brief snippet of documentation stating that the loader requires babel to be fully browser ready? This could serve as a warning to developers consuming the package to be fully aware of the risks.
If it is felt that this is unnecessary, at least at a minimum this issue will be available in history to help guide others who run into this similar state 馃槃
related to #76
babel-loader will be no longer needed once I release a stable version of 0.17.0, it will be replaced by vue-loader. Checkout the dev branch to see the configuration example.
@visualfanatic awesome. Thanks for the update!
Most helpful comment
babel-loaderwill be no longer needed once I release a stable version of0.17.0, it will be replaced byvue-loader. Checkout thedevbranch to see the configuration example.