Skip to content

Issues: webpack/loader-runner

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

11 Open 11 Closed
11 Open 11 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Loader options functions are not serialized correctly
#70 opened May 19, 2023 by janlent1
1
Loader cannot load ES6 script
#67 opened Sep 21, 2022 by markb-trustifi
3
I encountered some bad cases when using thread-loader on windows
#56 opened Jun 12, 2021 by YourWildDad
Feature proposal: Add getOptions to loaderContext inside runLoaders
#52 opened Mar 25, 2021 by marcalexiei
1
Should result.result be an array?
#51 opened Feb 13, 2021 by igoradamenko
1
Cannot find module if the path contains illegal character
#46 opened Jan 1, 2021 by csutorasa
1
Missing Support for this.resolve
#42 opened Jul 16, 2020 by emilyrohrbough
Add a way to share data across loaders for a given resource
#36 opened May 4, 2019 by romaricpascal
'this.fs' does not work from inside the module
#35 opened Mar 1, 2019 by renanmt
breaking change: 'fs' not longer available.
#34 opened Feb 12, 2019 by captnlima
2
refactoring to ES6?
#10 opened Jan 20, 2017 by tarang9211
4
ProTip! Add no:assignee to see everything that’s not assigned.