Janusz Janczy

I have the same problem

@dverkade have you managed to speed up the process ?

For now I use static:content-deploy - gulp babel / styles --prod (from frontools directory) - set of gulp tasks (from tools-rjs-optimizer directory*) *(based on frontools) - I've created similar tool...

- m2-tools-not-for-backend ;) - m2-front-dev-tools - falanouc, furcifer, etc. (some animal name that is on the list of endangered animals)

I also thought about m2-browser-tools - but it doesnt says it's frontend/backend (it says it just works or is for browser) Other idea as Christmas are coming: m2-magic-front-box / m2-front-magic-box...

I have this some issue even I had this deps added in my generated requirejs-config.js

@DrewML I've tested on M2.11.1 with snowdog/sass-blank and my gulp tasks that use `requirejs.optimize(config);` with Magento_BundleConfig module (from my own repo after changing php restriction from composer) Requirejs-config.js (function(require){ (function()...

@dverkade strange... as I still have it even after running setup:static-content:deploy..

@DrewML sure. It seems when I use Magento_BundleConfig to load bundles it show those errors even if in shared.js I have ``` !function(e){"function"==typeof define&&define.amd?define('jquery/jquery-storageapi',["jquery"],e) ``` if I add bundles by...

Adding jquery.cookie to jquery-migrate resolved my issues: ``` "shim": { "jquery/jquery-migrate": { "deps": [ "jquery", "jquery/jquery.cookie" ] }, ``` However will check few things on M2.1.11 and m2.3 with luma...