Support for webpack about brace HOT 10 CLOSED

Have a go at it and provide a PR. As long as it doesn't break current functionality (mainly working with browserify), I'm ok to merge it.

from brace.

Another solution is to use noParse webpack configuration:

noParse: [
"/brace/"
],

from brace.

Closing, but still open to a PR that adds this.

from brace.

Hey @joelgriffith, just FYI a fix was committed to webpack parser today for this: webpack/webpack@27b23c0

from brace.

Ah, nice so this works with webpack now as well as with browserify?

from brace.

Seems to so far :) Apologies that it is a bit off topic for this thread, but do you have any documentation for creating/using custom ACE modes with Brace? Many thanks!

from brace.

Not entirely sure, but there was a similar issue which had a solution: #14

from brace.

Awesome! I'll have to give it a spin sometime later.

from brace.

To be honest, now that the webpack parser bug has been fixed, webpack seems to be working fine with ACE itself (using src-noconflict)... Maybe Brace will be Browserify-only after all :D

from brace.

Well that's fine, I bet it doesn't inline workers though, so you'd still have to serve those.
Being able to browserify was just one reason I implemented brace, see

from brace.