You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And I have a main field specified in my package.json: "main": "src/main.js". If I have a relative import of index.js in SomeModule.js, it gets transpiled to the main field from the package.json.
importutilsfrom'.';// gets transpiled to '../../main'importutilsfrom'./';// works
Will try to look into where the resolution is coming from a bit more after work today.
The text was updated successfully, but these errors were encountered:
Replacing custom matcher with !path.isAbsolutePath() (reference)
Refining the regex to make slash optional
This leads me to a question: is there a reason to have a custom matcher? Is there any use case where resolving . to the current package.json main entry is the desired behavior?
I have a directory structure as follows:
And I have a
main
field specified in my package.json:"main": "src/main.js"
. If I have a relative import ofindex.js
inSomeModule.js
, it gets transpiled to the main field from the package.json.Will try to look into where the resolution is coming from a bit more after work today.
The text was updated successfully, but these errors were encountered: