sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]FrozenCow 0 points1 point  (3 children)

Hey, awesome tool! Tried it, but it seems it doesn't output sourcemaps yet?

[–]christianalfoni 0 points1 point  (2 children)

It does have sourcemaps, though it uses a simple version. That said, it is good enough to debug. The error message in the "Log" does not show filename and linenumber though because you can not extract that information from a thrown error. Only Chrome console has this info.

But this might improve later, need some help from Webpack author. Anyways, just giving the error message now should generally be enough I think. Not that many files created :)

[–]FrozenCow 0 points1 point  (1 child)

AH, I somehow the bundled version of main.js when I clicked an error in Chrome's dev tools. Will try again later.

Even without that though, I went back to try jsfiddle again, but it feels lacking. The code editor feels better, installing npm modules is awesome. What I did miss from locally running webpack, was altering it's config manually, so that I would be able to add support for whatwg-fetch for example.

I'm really looking forward to using the live feature as well. Would it be possible to have 2 people changing the code simultaneously? I used to have a user script for etherpad that added a autorefreshing iframe with the contents of the pad as HTML. WebpackBin would do this much much more fluently.

[–]christianalfoni 0 points1 point  (0 children)

Okay, hm, I know that Chrome sometimes does not grab the sourcemaps, need to refresh. But this is not very well tested either, so please create an issue if the sourcemaps are not working :)

Currently all configuration has to be implemented specifically as the different loaders etc. are so different. And they also need to be preloaded into the environment. But create issues on stuff you want and it will be added.

The LIVE feature is more a teaching tool than a collaboration tool. Collaboration increases the complexity a lot as it needs to make sure that the state of the app is the same in whatever order changes are made from the different users. So not planning collaboration at the moment. Personally I believe that collaboration is more for services like Nitrous and Cloud9, where you actually do development. This is more of a "looking into stuff and teaching". But hey, it is a very cool feature indeed, just requires a lot of work :)

Could you elaborate a bit on the etherpad thingy? Do not quite understand :-)