Skip to content
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.

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

Resolve against package.json main field #19

Open
arei opened this issue Jan 3, 2017 · 0 comments
Open

Resolve against package.json main field #19

arei opened this issue Jan 3, 2017 · 0 comments
Assignees

Comments

@arei
Copy link

arei commented Jan 3, 2017

I would like includepaths to resolve into a non-standard node_modules location for external entries. This sort of works, if the node_modules path is listed in the paths option. However, it only works for packages that have an index.js as their entry point. Many packages use different entry points as described in the main field of their package.json file. This request is then to resolve packages against their main field if a package.json exists.

A note as well that the package.json main field should resolve before just appending a index.js to the file name.

@darlanalves darlanalves self-assigned this Jan 23, 2018
@darlanalves darlanalves pinned this issue Jul 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants