webpack/loader-runner

Issues

• How to indicate that a loader uses ES modules

  #61 opened 2 years ago by morganney
  3

• Loader options functions are not serialized correctly

  #70 opened 2 years ago by janlent1
  1

• Loader cannot load ES6 script

  #67 opened 2 years ago by markb-trustifi
  3

• I encountered some bad cases when using thread-loader on windows

  #56 opened 4 years ago by YourWildDad
  0

• ES6 import error

  #38 opened 4 years ago by xgqfrms
  1

• breaking change: 'fs' not longer available.

  #34 opened 6 years ago by captnlima
  2

• Feature proposal: Add getOptions to loaderContext inside runLoaders

  #52 opened 4 years ago by marcalexiei
  1

• Cannot find module if the path contains illegal character

  #46 opened 4 years ago by csutorasa
  1

• Should `result.result` be an array?

  #51 opened 4 years ago by igoradamenko
  1

• Missing Support for `this.resolve`

  #42 opened 4 years ago by emilyrohrbough
  0

• Add a way to share data across loaders for a given resource

  #36 opened 6 years ago by romaricpascal
  0

• Issue with System module undefined error when running webpack 3.4.1 from custom gulp task

  #18 opened 7 years ago by mitchellmorris
  2

• 'this.fs' does not work from inside the module

  #35 opened 6 years ago by renanmt
  0

• If loader result Promise is Rejected, callback is called twice

  #29 opened 6 years ago by DeltaEvo
  2

• Could you please make new release?

  #9 opened 6 years ago by aindlq
  1

• Cannot load a module with Webpack 2.x

  #4 opened 6 years ago by koistya
  2

• Debugging SystemJS?

  #6 opened 6 years ago by jescalan
  2

• Avoid System.import?

  #16 opened 6 years ago by papandreou
  2

• parseQuery will be replaced with getOptions

  #19 opened 6 years ago by anlexN
  1

• Support `context.exec` feature?

  #2 opened 6 years ago by creeperyang
  1

• Missing license

  #28 opened 6 years ago by char0n
  7

• refactoring to ES6?

  #10 opened 8 years ago by tarang9211
  4