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 has been archived by the owner on Jan 2, 2018. It is now read-only.
We have some vendor files that are already webpacked, babelified etc. These files have a tendency to break if they run through babel-loader a second time. For the time being, we solve it like this in an action in our roc.config.js-file:
It would be really neat if the boilerplate can be hidden, and Roc provided a way to declaratively add paths/RegExps/modules to be hidden from the babel-loader:
The text was updated successfully, but these errors were encountered:
PAkerstrand
changed the title
Create a way to declaratively exclude modules/paths from babel-loaders
Create a way to declaratively exclude modules/paths from babel-loader
May 25, 2016
We have some vendor files that are already webpacked, babelified etc. These files have a tendency to break if they run through
babel-loader
a second time. For the time being, we solve it like this in an action in ourroc.config.js
-file:It would be really neat if the boilerplate can be hidden, and Roc provided a way to declaratively add paths/RegExps/modules to be hidden from the
babel-loader
:The text was updated successfully, but these errors were encountered: