Module not found: Error: Recursion in resolving

See original GitHub issue

🐞 Bug report

Command (mark with an x)

- [ ] new
- [ ] build
- [x] serve - (ng serve --aot)
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

Yes, the previous version in which this bug was not present was:

This error throw after update to “@angular/cli”: “^8.3.0” All was good with - “@angular/cli”: “^7.3.4”,

Description

Can’t serve project.

🔬 Minimal Reproduction

Build work after “ng update codelyzer” with another npm: devDependencies:

codelyzer ~4.2.1->~5.1.0
tslint ~5.9.1" -> ~5.19.0
typescript ~3.2.4 -> 3.5.3
@angular/compiler-cli ^7.2.2 -> ^8.2.3
@angular/language-service ^7.2.2 -> 8.2.3

dependencies:

@angular/animations ^7.2.7 -> ^8.2.3
@angular/common ^7.2.7 -> ^8.2.3
@angular/compiler ^7.2.7 -> ^8.2.3
@angular/core ^7.2.7 -> ^8.2.3
@angular/forms ^7.2.7 -> ^8.2.3
@angular/platform-browser ^7.2.7 -> ^8.2.3
@angular/platform-browser-dynamic ^7.2.7 -> ^8.2.3
@angular/router ^7.2.7 -> ^8.2.3
zone.js ^0.8.29 -> ^0.9.1

And error throw after “ng update @angular/cli @angular/core”

@angular-devkit/build-angular ^7.3.4 -> ~0.803.0
@angular/cli ^7.3.4 -> ^8.3.0

I try to update all package to latest version with npm-check-updates, but didn’t help to me.

🔥 Exception or Error


ERROR in ./node_modules/@auth0/angular-jwt/src/jwt.interceptor.js
Module not found: Error: Recursion in resolving
Stack:
  resolve: (C:\Git\proj\node_modules\@auth0\angular-jwt\src) url
  newResolve: (C:\Git\proj\node_modules\@auth0\angular-jwt\src) url
  parsedResolve: (C:\Git\proj\node_modules\@auth0\angular-jwt\src) url module
  describedResolve: (C:\Git\proj\node_modules\@auth0\angular-jwt\src) url module
  resolve: (C:\Git\proj\node_modules\@auth0\angular-jwt\src) C:\Git\proj\node_modules\url\url.js module
  newResolve: (C:\Git\proj\node_modules\@auth0\angular-jwt\src) C:\Git\proj\node_modules\url\url.js module
  parsedResolve: (C:\Git\proj\node_modules\@auth0\angular-jwt\src) C:\Git\proj\node_modules\url\url.js
  describedResolve: (C:\Git\proj\node_modules\@auth0\angular-jwt\src) C:\Git\proj\node_modules\url\url.js
  resolve: (C:\Git\proj\node_modules\@auth0\angular-jwt\src) C:\Git\proj\node_modules\url\url.js
  newResolve: (C:\Git\proj\node_modules\@auth0\angular-jwt\src) C:\Git\proj\node_modules\url\url.js


ERROR in (webpack)-dev-server/client/utils/createSocketUrl.js
Module not found: Error: Recursion in resolving
Stack:
  resolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) querystring
  newResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) querystring
  parsedResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) querystring module
  describedResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) querystring module
  resolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\querystring-es3\index.js module
  newResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\querystring-es3\index.js module
  parsedResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\querystring-es3\index.js
  describedResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\querystring-es3\index.js
  resolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\querystring-es3\index.js
  newResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\querystring-es3\index.js


ERROR in (webpack)-dev-server/client/utils/createSocketUrl.js
Module not found: Error: Recursion in resolving
Stack:
  resolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) url
  newResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) url
  parsedResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) url module
  describedResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) url module
  resolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\url\url.js module
  newResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\url\url.js module
  parsedResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\url\url.js
  describedResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\url\url.js
  resolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\url\url.js
  newResolve: (C:\Git\proj\node_modules\webpack-dev-server\client\utils) C:\Git\proj\node_modules\url\url.js


ERROR in (webpack)/hot/emitter.js
Module not found: Error: Recursion in resolving
Stack:
  resolve: (C:\Git\proj\node_modules\webpack\hot) events
  newResolve: (C:\Git\proj\node_modules\webpack\hot) events
  parsedResolve: (C:\Git\proj\node_modules\webpack\hot) events module
  describedResolve: (C:\Git\proj\node_modules\webpack\hot) events module
  resolve: (C:\Git\proj\node_modules\webpack\hot) C:\Git\proj\node_modules\webpack\node_modules\events\events.js module
  newResolve: (C:\Git\proj\node_modules\webpack\hot) C:\Git\proj\node_modules\webpack\node_modules\events\events.js module
  parsedResolve: (C:\Git\proj\node_modules\webpack\hot) C:\Git\proj\node_modules\webpack\node_modules\events\events.js
  describedResolve: (C:\Git\proj\node_modules\webpack\hot) C:\Git\proj\node_modules\webpack\node_modules\events\events.js
  resolve: (C:\Git\proj\node_modules\webpack\hot) C:\Git\proj\node_modules\webpack\node_modules\events\events.js
  newResolve: (C:\Git\proj\node_modules\webpack\hot) C:\Git\proj\node_modules\webpack\node_modules\events\events.js

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
clydincommented, Aug 27, 2019

The usage of the * in the following is unneeded:

    "paths": {
      "*": [
        "*",
        "app/*",
        "environments/*"
      ]
    }

If a match isn’t found at the specified paths, standard resolution will occur.

0reactions
angular-automatic-lock-bot[bot]commented, Sep 27, 2019

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Solve - Module not found: Recursion in resolving - NPM
I have solved this problem. A conflict between node modules and package.json was the reason. I've created a new React Application using npx ......
Read more >
ng build Module not found: Error: Recursion in resolving #18021
Bug report Command (mark with an x) new build serve test e2e generate add update lint xi18n run config help version doc Is...
Read more >
Module not found: Error: Recursion in resolving - jQWidgets
Hi, Im new to jqwidgets, currently Im using jqwidgets-ng, I have created an Angular app using the npm package create-jqwidgets-angular-app ...
Read more >
Module not found: Error: Recursion in resolving in angular app ...
I found the argument --preserveSymlinks when passed to ng test (that is where I am seeing the error) will break the recursion (fix)...
Read more >
How to fix 'Module not found: Can't resolve 'http' in ... - YouTube
Basically, just change 'react-scripts' to 4.0.2 in your package.json and run `npm install` again :D Follow me on Twitter: ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found