Closed krainboltgreene closed 7 years ago
Turns out this was node-fs-extra's fault, but since it depends on it I suggest keeping this open until they fix and have an update pushed.
I also still suggest using checksums for the property names, since filenames can be really crazy.
Nah, there was a real issue in browserify-hmr here. Turns out if you do someString.replace(foo, bar)
, then if bar
is a string with $
characters, they get treated specially. The fix was to change bar
to be a function that returns a string, which .replace doesn't do anything special with.
Fixed in browserify-hmr 0.3.2.
Ran into this error:
Turns out there's a bug with the filenames?
Have you considered checksums?