Closed cedricziel closed 8 years ago
In my main.js, I have included a library:
requirejs.config({ //.. paths: { //.. 'angular-ui-select': '../../bower_components/angular-ui-select/dist/select.min', //.. } });
In the build.js, it is being externalized via empty:.
empty:
What happens is that on processing, the resulting file that is delivered in production is
function..... (the libraries content) define("angular-ui-select", ["angular"], (function (global) { return function () { var ret, fn; return ret || global.angular; }; } ..
As you can see, the wrapper is not generated around, but after the libraries' content.
Am I missing something or is this a bug?
No clue if the issue still persists. Will close to clean my and your tracker.
In my main.js, I have included a library:
In the build.js, it is being externalized via
empty:
.What happens is that on processing, the resulting file that is delivered in production is
As you can see, the wrapper is not generated around, but after the libraries' content.
Am I missing something or is this a bug?