Julian

@matthewp thanks, that was the problem. i think we should create a "troubleshooting" page. there we can put some other stuff like * https://stealjs.com/docs/StealJS.using-npm-packages.html#troubleshooting-troublesome-packages * explain so error messages https://stealjs.com/docs/StealJS.error-messages.html#mismatched-package-version...

@m-mujica he said > If I build with sourceMaps: true (and --->>> minify: false

the actual intention was to create a module that hardly ever changes. this code can be cached very well. any other ideas how to make this work?

what does steal-tools have to do with laravel? you can create your javascript bundle without interupt laravel. Or do you want to know how to structure the javascript files inside...

i think `bundleAssets` will not cause that `normalize.css` will copyed into the dist folder, because we dont build a dependency graph of css files that are imported by CSS. @m-mujica...

hey @justinbmeyer i think the locking mechanism will do the job. is can.connect working with streams? maybe we can merge that streams?

This is not the right jsbin, isn't it?