Skip to content
Snippets Groups Projects
Select Git revision
  • topic/default/bytes
  • branch/default default protected
  • 0.4.1 protected
  • 0.4.2 protected
  • 0.6.0 protected
  • 0.6.1 protected
  • ra-cubicweb@0.1.0 protected
  • ra-cubicweb@0.1.1 protected
  • ra-cubicweb@0.2.0 protected
  • ra-cubicweb@0.2.1 protected
  • ra-cubicweb@0.2.2 protected
  • ra-cubicweb@0.2.3 protected
  • ra-cubicweb@0.3.0 protected
  • ra-cubicweb@0.4.0 protected
  • ra-cubicweb@0.4.3 protected
  • ra-cubicweb@0.4.4 protected
  • v0.5.0 protected
17 results
Blame Permalink
  • Frank Bessou's avatar
    18429c2b38f1
    chore: include third-pary source maps in demo build · 18429c2b38f1
    Frank Bessou authored 
    The source maps allow the browser to display original files in the
debugger and in the console.
By default, webpack only includes source maps generated in the current
build. It doesn't include source maps located in node_modules. The
source-map-loader npm packages allow webpack to discover third-party
source maps and the `"devtool": "eval-source-map"` strategy makes
webpack expose both loaded source maps and generated source maps to the
browser.
    18429c2b38f1
    History
    chore: include third-pary source maps in demo build
    Frank Bessou authored 
    The source maps allow the browser to display original files in the
debugger and in the console.
By default, webpack only includes source maps generated in the current
build. It doesn't include source maps located in node_modules. The
source-map-loader npm packages allow webpack to discover third-party
source maps and the `"devtool": "eval-source-map"` strategy makes
webpack expose both loaded source maps and generated source maps to the
browser.
This project manages its dependencies using Yarn. Learn more