Open deathcap opened 9 years ago
to investigate: node-minecraft-protocol adds its own source maps with gulp-sourcemaps (https://github.com/PrismarineJS/node-minecraft-protocol/pull/115), are they conflicting with browserify source maps? dist/protocol.js //# sourceMappingURL=maps/protocol.js.map
, separate files added in dist/maps
, versus browserify's inline maps, which might be different when they are bundled along with all other modules into bundle.js (can source maps be nested??)
Chrome 41.0.2272.89, mcwebchat example, while debugging with breakpoints sometimes shows:
waiting a while, no change. Reloading usually fixes this problem however.
Haven't seen this problem with a larger browserify-based project https://github.com/deathcap/voxelmetaverse not clear what is different in wsmc/mcwebchat