Skip to content

Issues: browserify/resolve

Beta
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

Clear current search query, filters, and sorts
9 Open 157 Closed
9 Open 157 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
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

central issue for "default extensions"
#166 opened Jun 16, 2018 by ljharb updated Jul 12, 2018
2
12
Support a promise API
#210 opened Feb 5, 2020 by SimenB updated Nov 30, 2020
2
Does the require.resolve paths option work just like the baseDir option?
#188 opened Mar 20, 2019 by watson updated Jan 4, 2022
9
custom path module
#267 opened Jan 7, 2022 by mafintosh updated Jan 28, 2022
15
Improvement idea - globally configurable helper functions
#280 opened Apr 22, 2022 by naugtur updated Apr 23, 2022
3
Unable to resolve a package by its own name
#289 opened Aug 14, 2022 by fasttime updated Oct 13, 2022
2
Result differs from Node's require.resolve when using basedir option with symlinks
#295 opened Jan 27, 2023 by j-christoffersen updated Jan 27, 2023
9
Support ESM resolution
#222 opened Apr 25, 2020 by SimenB updated Apr 4, 2024
37
Node.js imports field is not supported
#327 opened Nov 24, 2024 by pcdevil updated Nov 30, 2024
3
ProTip! Updated in the last three days: updated:>2025-05-04.