Giters
webpack
/
loader-runner
Runs (webpack) loaders
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
294
Watchers:
10
Issues:
22
Forks:
59
webpack/loader-runner Issues
How to indicate that a loader uses ES modules
Closed
10 months ago
Comments count
3
Loader options functions are not serialized correctly
Updated
a year ago
Comments count
1
Loader cannot load ES6 script
Updated
2 years ago
Comments count
3
I encountered some bad cases when using thread-loader on windows
Updated
3 years ago
ES6 import error
Closed
3 years ago
Comments count
1
breaking change: 'fs' not longer available.
Updated
3 years ago
Comments count
2
Feature proposal: Add getOptions to loaderContext inside runLoaders
Updated
3 years ago
Comments count
1
Cannot find module if the path contains illegal character
Updated
3 years ago
Comments count
1
Should `result.result` be an array?
Updated
3 years ago
Comments count
1
Missing Support for `this.resolve`
Updated
4 years ago
Add a way to share data across loaders for a given resource
Updated
5 years ago
Issue with System module undefined error when running webpack 3.4.1 from custom gulp task
Closed
7 years ago
Comments count
2
'this.fs' does not work from inside the module
Updated
5 years ago
If loader result Promise is Rejected, callback is called twice
Closed
5 years ago
Comments count
2
Could you please make new release?
Closed
5 years ago
Comments count
1
Cannot load a module with Webpack 2.x
Closed
5 years ago
Comments count
2
Debugging SystemJS?
Closed
5 years ago
Comments count
2
Avoid System.import?
Closed
5 years ago
Comments count
2
parseQuery will be replaced with getOptions
Closed
5 years ago
Comments count
1
Support `context.exec` feature?
Closed
5 years ago
Comments count
1
Missing license
Closed
5 years ago
Comments count
7
refactoring to ES6?
Updated
7 years ago
Comments count
4