-
Notifications
You must be signed in to change notification settings - Fork 43
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
Recursion in resolving #38
Comments
FYI, I "workedaround" by removing some code out for the transformation so it's not urgent by might be nice to have a clue :) |
The best of unmaintained modules their not change so fast :-) PS: |
Want to say boost is superfast changing library in C++ world, but looks like js world is mad. |
Hey! I'm trying to integrate AVA/webpack into our stack and so naturally that path lead me here. I'm running into a similar issue where our resolver is modularizing all our level folders. Because of this issue the files in those folders can't require other files (their siblings) from the same folder. So for example, for the following file structure:
I've got the following resolve config:
And, while I can do the following in a container and
Attempting to import other subsequent components inside the
|
I am currently replacing some old node code build by webpack by your plugin and got this weird error
(I have no idea how to fix it as I am writing this).
I am seeing that your are using "enhanced-resolve", but I am also seeing that this module is unmaintained (per description https://github.com/webpack/enhanced-require at the top of the page).
The module that seems to create a recursion is the resolution of the "github" package, no idea why this one...
Any idea?
The text was updated successfully, but these errors were encountered: