question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Production build removes important information from error

See original GitHub issue

🐞 Bug report

Command (mark with an x)

  • new
  • build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • extract-i18n
  • run
  • config
  • help
  • version
  • doc

Is this a regression?

Yes, it was working in some previous ng versions

Description

Production minified build remove importannt information from error, while dev stays correct

🔬 Minimal Reproduction

Create app, make service with some unknown parameters

🔥 Exception or Error

DEV


Uncaught Error: NG0204: Can't resolve all parameters for AuthHttpInterceptor: (?, ?, ?).
    at getUndecoratedInjectableFactory (core.mjs:6940:15)
    at injectableDefOrInjectorDefFactory (core.mjs:6930:16)
    at providerToFactory (core.mjs:6998:51)
    at providerToRecord (core.mjs:6960:25)
    at R3Injector.processProvider (core.mjs:6863:24)
    at core.mjs:6694:59
    at forEachSingleProvider (core.mjs:7034:13)
    at forEachSingleProvider (core.mjs:7031:13)
    at new R3Injector (core.mjs:6694:9)
    at new EnvironmentNgModuleRefAdapter (core.mjs:21774:26)

PROD


Uncaught Error: NG0204
    at ko (main.bae0f627af79e371.js:1:544663)
    at sc (main.bae0f627af79e371.js:1:545181)
    at dh (main.bae0f627af79e371.js:1:545572)
    at Q0 (main.bae0f627af79e371.js:1:543856)
    at la.processProvider (main.bae0f627af79e371.js:1:543866)
    at main.bae0f627af79e371.js:1:541614
    at bd (main.bae0f627af79e371.js:1:545810)
    at bd (main.bae0f627af79e371.js:1:545786)
    at new la (main.bae0f627af79e371.js:1:541601)
    at new ig (main.bae0f627af79e371.js:1:588517)
    at yf (main.bae0f627af79e371.js:1:588800)
    at main.bae0f627af79e371.js:1:609449
    at v.invoke (polyfills.d621b0e3244453cd.js:1:6539)
    at Object.onInvoke (main.bae0f627af79e371.js:1:604415)
    at v.invoke (polyfills.d621b0e3244453cd.js:1:6479)
    at M.run (polyfills.d621b0e3244453cd.js:1:1935)
    at Qo.run (main.bae0f627af79e371.js:1:605036)
    at jD (main.bae0f627af79e371.js:1:609432)
    at on (main.bae0f627af79e371.js:1:634979)
    at 2730 (main.bae0f627af79e371.js:1:275935)
    at r (runtime.c90347ac34a249b3.js:1:143)
    at main.bae0f627af79e371.js:1:802061
    at n (runtime.c90347ac34a249b3.js:1:2856)
    at main.bae0f627af79e371.js:1:47

🌍 Your Environment


Angular CLI: 14.1.1
Node: 14.18.2
Package Manager: yarn 3.2.1
OS: win32 x64

Angular: 14.1.1
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1401.1 (cli-only)
@angular-devkit/build-angular   14.1.1
@angular-devkit/core            14.1.1 (cli-only)
@angular-devkit/schematics      14.1.1 (cli-only)
@schematics/angular             14.1.1 (cli-only)
rxjs                            7.5.6
typescript                      4.7.4

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
alan-agius4commented, Aug 9, 2022

Why you don’t want to include that? In theory prod build can produce result different than dev, so might be situation when this error do not occur in dev

That shouldn’t not happen.

0reactions
angular-automatic-lock-bot[bot]commented, Sep 9, 2022

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

On production build getting ' Uncaught (in promise): Error
This removes the uglification during build so the error log contains the missing ... Are you using any service to get data from...
Read more >
Remove Errors handlers in the production build. : r/angular
When I generate my production build everything works perfectly but I was wondering about all those "Errors Thrown" in the Angular (main.js) ...
Read more >
Error handling - Apollo GraphQL Docs
The unwrapResolverError function can remove the GraphQLError wrapping from a resolver error or return the error unaltered if it isn't from a resolver....
Read more >
ng build - Angular
Option Description Value Type Default Value ‑‑aot Build using Ahead of Time compilation. boolean true ‑‑base‑href Base url for the application being built. string ‑‑delete‑output‑path Delete...
Read more >
Human error: models and management - PMC - NCBI - NIH
Understanding these differences has important practical implications for coping with the ever present risk of mishaps in clinical practice. Summary points. Two ...
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