The npm package `lodash` itself is not an ECMAScript module and therefore produces the warning.
There are multiple ways to fix this:

## Replace with ES modulized library (recommended)

Some libraries offer ES modulized builds. In case of `lodash`, you can replace it with [lodash-es](https://www.npmjs.com/package/lodash-es).

Run `npm install --save lodash-es`.

Now replace all imports from `lodash` with `lodash-es`.

Also make sure to import the library with ES import statements:

```javascript
import { keys } from &#39;lodash-es&#39;;
```

## Whitelist CommonJS dependency

If there is no ES modulized build available for your library, or if you for some reason don&#39;t care, you can allow specific CommonJS dependencies in the `angular.json` file:

```json
&quot;architect&quot;: {
  &quot;build&quot;: {
    &quot;builder&quot;: &quot;@angular-devkit/build-angular:browser&quot;,
    &quot;options&quot;: {
      &quot;allowedCommonJsDependencies&quot;: [&quot;lodash&quot;]
    }
  }
}

```

&gt; Since Angular CLI Version 10.0.1 you can use globs in `allowedCommonJsDependencies`.
&gt; This means that if you pass `lodash`, the sub-paths (e.g. `lodash/keys`) will also be allowed.

Docs reference: https://angular.io/guide/build#configuring-commonjs-dependencies

I was told that the following code has undefined behavior until C++20:

    int *p = (int*)malloc(sizeof(int));
    *p = 10;

Is that true?

The argument was that the lifetime of the `int` object is not started before assigning the value to it ([P0593R6][1]). To fix the problem, placement `new` should be used:

    int *p = (int*)malloc(sizeof(int));
    new (p) int;
    *p = 10;

Do we really have to call a default constructor that is trivial to start the lifetime of the object?

At the same time, the code does not have undefined behavior in pure C. But, what if I allocate an `int` in C code and use it in C++ code?

    // C source code:
    int *alloc_int(void)
    {
        int *p = (int*)malloc(sizeof(int));
        *p = 10;
        return p;
    }

    // C++ source code:
    extern &quot;C&quot; int *alloc_int(void);

    auto p = alloc_int();
    *p = 20;

Is it still undefined behavior?

  [1]: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p0593r6.html#motivating-examples

Is using malloc for int undefined behavior until C++20

Good afternoon, please tell me what I&#39;m doing wrong. I just installed the Linux Ubuntu on my computer and still don’t understand anything about it. I tried to install PostreSQL and pgAdmin. I installed on this video tutorial `https://www.youtube.com/watch?v=Vdzb7JTPnGk` I get this error.

Text of Error: `Skipping acquire of configured file &#39;main/binary-i386/Packages&#39; as repository &#39;http://apt.postgresql.org/pub/repos/apt focal-pgdg InRelease&#39; doesn&#39;t support architecture &#39;i386&#39;`

  ![](https://i.stack.imgur.com/tm6Gr.png)

Tell me please how to fix it. 
My version of ubuntu: `Ubuntu 20.04 LTS`




Skipping acquire of configured file &#39;main/binary-i386/Packages&#39;

I am trying to upgrade my Angular 9 app to Angular 10 version, but getting below warning after the upgrade 

    WARNING in calendar.reducer.ts depends on lodash/keys. CommonJS or AMD dependencies can cause optimization bailouts.

I have added below line to my `angular.json` file but issue is not resolved 

    &quot;allowedCommonJsDependencies&quot;: [&quot;lodash&quot;]

How can I fix above issue.

Angular 10 Upgrade - Fix CommonJS or AMD dependencies can cause optimization bailouts

I am trying to upgrade my Angular 9 app to Angular 10 version, but getting below warning after the upgrade
<pre><code class="hljs language-bash">WARNING in calendar.reducer.ts depends on lodash/keys. CommonJS or AMD dependencies can cause optimization bailouts.
</code></pre>
I have added below line to my <code>angular.json</code> file but issue is not resolved
<pre><code class="hljs language-json">"allowedCommonJsDependencies": ["lodash"]
</code></pre>
How can I fix above issue.

I am trying to upgrade my angular 9 app to angular 10 version, but getting below warning after the upgrade

```
rxjs\BehaviorSubject.js depends on rxjs-compat/BehaviorSubject
```

Any idea how to fix this?

Upgrading to Angular 10 - Fix CommonJS or AMD dependencies can cause optimization bailouts

The issue was that I was trying to POST to https when that API actually only supports HTTP.
Just leave this as a note for other folks who might run into the same issue.

Any Help can be appreciated

Error: write EPROTO 34557064:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc:242:

# Preface

**This issue seems to only affect Chrome/V8, and may not be reproducible in Firefox or other browsers**. In summary, the execution time of a function callback increases by an order of magnitude or more if the function is called with a new callback anywhere else. 

## Simplified Proof-of-Concept

Calling `test(callback)` arbitrarily many times works as expected, but once you call `test(differentCallback)`, the execution time of the `test` function increases dramatically no matter what callback is provided (i.e., another call to `test(callback)` would suffer as well). 

**This example was updated to use arguments so as to not be optimized to an empty loop. Callback arguments `a` and `b` are summed and added to `total`, which is logged.** 

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    function test(callback) {
        let start = performance.now(),
            total = 0;

        // add callback result to total
        for (let i = 0; i &lt; 1e6; i++)
            total += callback(i, i + 1);

        console.log(`took ${(performance.now() - start).toFixed(2)}ms | total: ${total}`);
    }

    let callback1 = (a, b) =&gt; a + b,
        callback2 = (a, b) =&gt; a + b;

    console.log(&#39;FIRST CALLBACK: FASTER&#39;);
    for (let i = 1; i &lt; 10; i++)
        test(callback1);

    console.log(&#39;\nNEW CALLBACK: SLOWER&#39;);
    for (let i = 1; i &lt; 10; i++)
        test(callback2);

&lt;!-- end snippet --&gt;

---

## Original post

I am developing a `StateMachine` class ([source][1]) for a library I&#39;m writing and the logic works as expected, but in profiling it, I&#39;ve run into an issue. I noticed that when I ran the profiling snippet (in global scope), it would only take about 8ms to finish, but if I ran it a second time, it would take up to 50ms and eventually balloon as high as 400ms. Typically, running the same named function over and over will cause its execution time to *drop* as the V8 engine optimizes it, but the opposite seems to be happening here. 

I&#39;ve been able to get rid of the problem by wrapping it in a closure, but then I noticed another weird side effect: Calling a different function that relies on the `StateMachine` class would break the performance for all code depending on the class. 

The class is pretty simple - you give it an initial state in the constructor or `init`, and you can update the state with the `update` method, which you pass a callback that accepts `this.state` as an argument (and usually modifies it). `transition` is a method that is used to `update` the state until the `transitionCondition` is no longer met.

Two test functions are provided: `red` and `blue`, **which are identical**, and each will generate a `StateMachine` with an initial state of `{ test: 0 }` and use the `transition` method to `update` the state while `state.test &lt; 1e6`. The end state is `{ test: 1000000 }`.

You can trigger the profile by clicking the red or blue button, which will run `StateMachine.transition` 50 times and log the average time the call took to complete. If you click the red or blue button repeatedly, you will see that it clocks in at less than 10ms without issue - *but*, once you click the *other* button and call the other version of the same function, everything breaks, and the execution time for both functions will increase by about an order of magnitude. 

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    // two identical functions, red() and blue()

    function red() {
      let start = performance.now(),
          stateMachine = new StateMachine({
            test: 0
          });

      stateMachine.transition(
        state =&gt; state.test++, 
        state =&gt; state.test &lt; 1e6
      );

      if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
      else return performance.now() - start;
    }

    function blue() {
      let start = performance.now(),
          stateMachine = new StateMachine({
            test: 0
          });

      stateMachine.transition(
        state =&gt; state.test++, 
        state =&gt; state.test &lt; 1e6
      );

      if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
      else return performance.now() - start;
    }

    // display execution time
    const display = (time) =&gt; document.getElementById(&#39;results&#39;).textContent = `Avg: ${time.toFixed(2)}ms`;

    // handy dandy Array.avg()
    Array.prototype.avg = function() {
      return this.reduce((a,b) =&gt; a+b) / this.length;
    }

    // bindings
    document.getElementById(&#39;red&#39;).addEventListener(&#39;click&#39;, () =&gt; {
      const times = [];
      for (var i = 0; i &lt; 50; i++)
        times.push(red());
        
      display(times.avg());
    }),

    document.getElementById(&#39;blue&#39;).addEventListener(&#39;click&#39;, () =&gt; {
      const times = [];
      for (var i = 0; i &lt; 50; i++)
        times.push(blue());
        
      display(times.avg());
    });

&lt;!-- language: lang-html --&gt;

    &lt;script src=&quot;https://cdn.jsdelivr.net/gh/TeleworkInc/state-machine@bd486a339dca1b3ad3157df20e832ec23c6eb00b/StateMachine.js&quot;&gt;&lt;/script&gt;

    &lt;h2 id=&quot;results&quot;&gt;Waiting...&lt;/h2&gt;
    &lt;button id=&quot;red&quot;&gt;Red Pill&lt;/button&gt;
    &lt;button id=&quot;blue&quot;&gt;Blue Pill&lt;/button&gt;

    &lt;style&gt;
    body{box-sizing:border-box;padding:0 4rem;text-align:center}button,h2,p{width:100%;margin:auto;text-align:center;font-family:-apple-system,BlinkMacSystemFont,&quot;Segoe UI&quot;,Roboto,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;,&quot;Segoe UI Symbol&quot;}button{font-size:1rem;padding:.5rem;width:180px;margin:1rem 0;border-radius:20px;outline:none;}#red{background:rgba(255,0,0,.24)}#blue{background:rgba(0,0,255,.24)}
    &lt;/style&gt;

&lt;!-- end snippet --&gt;

# Updates
### [&lt;strike&gt;Bug Report&lt;/strike&gt; &quot;Feature Request&quot; filed](https://bugs.chromium.org/p/v8/issues/detail?id=10676) (awaiting update) - See @jmrk&#39;s answers below for more details. 

Ultimately, this behavior is unexpected and, IMO, qualifies as a nontrivial bug. The impact for me is significant - on Intel i7-4770 (8) @ 3.900GHz, my execution times in the example above go from an average of 2ms to 45ms (a 20x increase).

As for nontriviality, consider that any *subsequent* calls to `StateMachine.transition`  after the first one will be unnecessarily slow, regardless of scope or location in the code. The fact that SpiderMonkey does not slow down subsequent calls to `transition` signals to me that there is room for improvement for this specific optimization logic in V8.

See below, where subsequent calls to `StateMachine.transition` are slowed:

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    // same source, several times

    // 1
    (function() {
      let start = performance.now(),
        stateMachine = new StateMachine({
          test: 0
        });

      stateMachine.transition(state =&gt; state.test++, state =&gt; state.test &lt; 1e6);

      if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
      console.log(`took ${performance.now() - start}ms`);
    })();


    // 2 
    (function() {
      let start = performance.now(),
        stateMachine = new StateMachine({
          test: 0
        });

      stateMachine.transition(state =&gt; state.test++, state =&gt; state.test &lt; 1e6);

      if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
      console.log(`took ${performance.now() - start}ms`);
    })();

    // 3
    (function() {
      let start = performance.now(),
        stateMachine = new StateMachine({
          test: 0
        });

      stateMachine.transition(state =&gt; state.test++, state =&gt; state.test &lt; 1e6);

      if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
      console.log(`took ${performance.now() - start}ms`);
    })();

&lt;!-- language: lang-html --&gt;

    &lt;script src=&quot;https://cdn.jsdelivr.net/gh/TeleworkInc/state-machine@bd486a339dca1b3ad3157df20e832ec23c6eb00b/StateMachine.js&quot;&gt;&lt;/script&gt;

&lt;!-- end snippet --&gt;

This performance decrease can be avoided by wrapping the code in a *named* closure, where presumably the optimizer knows the callbacks will not change:

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    var test = (function() {
        let start = performance.now(),
            stateMachine = new StateMachine({
                test: 0
            });
      
        stateMachine.transition(state =&gt; state.test++, state =&gt; state.test &lt; 1e6);
      
        if (stateMachine.state.test !== 1e6) throw &#39;ASSERT ERROR!&#39;;
        console.log(`took ${performance.now() - start}ms`);
    });

    test();
    test();
    test();

&lt;!-- language: lang-html --&gt;

    &lt;script src=&quot;https://cdn.jsdelivr.net/gh/TeleworkInc/state-machine@bd486a339dca1b3ad3157df20e832ec23c6eb00b/StateMachine.js&quot;&gt;&lt;/script&gt;

&lt;!-- end snippet --&gt;

&lt;h1&gt;Platform Information&lt;/h1&gt;

```none
$ uname -a
Linux workspaces 5.4.0-39-generic #43-Ubuntu SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

$ google-chrome --version
Google Chrome 83.0.4103.116
```


  [1]: https://cdn.jsdelivr.net/gh/TeleworkInc/StateMachine.js@bd486a339dca1b3ad3157df20e832ec23c6eb00b/StateMachine.js
  [2]: https://bugs.chromium.org/p/v8/issues/detail?id=10676

Why is the execution time of this function call changing?

Here is my simple graphql express app

    const express = require(&#39;express&#39;);
    const graphqlHTTP = require(&#39;express-graphql&#39;);
    
    const app = express();
    app.use(
        &#39;/graphql&#39;,
        graphqlHTTP({
          graphiql: true,
        })
      );
    
    app.listen(4000, () =&gt; {
        console.log(&quot;listening for request!&quot;);
    });

I&#39;m getting the following errors when I run it:

     graphqlHTTP({
        ^
    
    TypeError: graphqlHTTP is not a function
        at Object.&lt;anonymous&gt; (D:\PersonalProjects\GraphQL\server\app.js:7:5)
        at Module._compile (internal/modules/cjs/loader.js:1138:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
        at Module.load (internal/modules/cjs/loader.js:986:32)
        at Function.Module._load (internal/modules/cjs/loader.js:879:14)
        at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)  
        at internal/main/run_main_module.js:17:47

How can I fix it? Thanks in advance!

graphqlHTTP is not a function

The documentation page: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/replaceAll

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    let string = &quot;:insertx: :insertx: :inserty: :inserty: :insertz: :insertz:&quot;;
    let newstring = string.replaceAll(&quot;:insertx:&quot;, &#39;hello!&#39;);

&lt;!-- end snippet --&gt;

When I run this, I receive `Uncaught TypeError: string.replaceAll is not a function`. Maybe I&#39;m misunderstanding what a prototype is, but the function appears to be a string method that is available for use.

I&#39;m using Chrome.

Javascript .replaceAll() is not a function type error

After upgrading from Angular version 8 to 10. 

Running the - ng serve command gives me error - 


ERROR in node_modules/ngx-tree-select/src/module.d.ts:11:56 - error TS2314: Generic type &#39;ModuleWithProviders&lt;T&gt;&#39; requires 1 type argument(s).

11     static forRoot(options: TreeSelectDefaultOptions): ModuleWithProviders;
                                                        ~~~~~~~~~~~~~~~~~~~

This is my file - fronent/webapp/node_modules/ngx-tree-select/src/module.d.ts
 
    import { ModuleWithProviders } from &#39;@angular/core&#39;;
    import { TreeSelectDefaultOptions } from &#39;./models/tree-select-default-options&#39;;
    import * as ɵngcc0 from &#39;@angular/core&#39;;
    import * as ɵngcc1 from &#39;./components/tree-select.component&#39;;
    import * as ɵngcc2 from &#39;./components/tree-select-item.component&#39;;
    import * as ɵngcc3 from &#39;./directives/off-click.directive&#39;;
    import * as ɵngcc4 from &#39;./pipes/item.pipe&#39;;
    import * as ɵngcc5 from &#39;@angular/common&#39;;
    import * as ɵngcc6 from &#39;@angular/forms&#39;;
    export declare class NgxTreeSelectModule {
        static forRoot(options: TreeSelectDefaultOptions): ModuleWithProviders;
        static ɵmod: ɵngcc0.ɵɵNgModuleDefWithMeta&lt;NgxTreeSelectModule, [typeof ɵngcc1.TreeSelectComponent, typeof ɵngcc2.TreeSelectItemComponent, typeof ɵngcc3.OffClickDirective, typeof ɵngcc4.ItemPipe], [typeof ɵngcc5.CommonModule, typeof ɵngcc6.FormsModule], [typeof ɵngcc1.TreeSelectComponent]&gt;;
        static ɵinj: ɵngcc0.ɵɵInjectorDef&lt;NgxTreeSelectModule&gt;;
    }
    
    //# sourceMappingURL=module.d.ts.map


Kindly view the image for the error.

[![enter image description here][1]][1]



  [1]: https://i.stack.imgur.com/rzcl5.png

Angular error - Generic type &#39;ModuleWithProviders&lt;T&gt;&#39; requires 1 type argument(s)

I have some components like `CricketComponent`, `FootballComponent`, `TennisComponent` etc. All These Classes have some common properties :- `TeamName, teamSize, players` etc which are `@Input()`. 

Now I created a `BaseComponent` class, defined all these properties in there and this `baseComponent` class will be extended by cricket/football/tennis/etcComponents. 

baseComponent.ts

    export class BaseComponent {
    
        @Input() TeamName: string;
        @Input() teamSize: number;
        @Input() players: any;
    
    }

CricketComponent.ts


    @Component({
      selector: &#39;app-cricket&#39;,
      templateUrl: &#39;./cricket.component.html&#39;,
      styleUrls: [&#39;./cricket.component.scss&#39;]
    })
    export class cricketComponent extends BaseComponent implements OnInit {
    
      constructor() {
        super();
      }
    
      ngOnInit(): void {
      }
    
    }

I am getting this error:

ERROR in src/app/base-screen.ts:4:14 - error NG2007:

**Class is using Angular features but is not decorated. Please add an explicit Angular decorator.**

Class is using Angular features but is not decorated. Please add an explicit Angular decorator

I want to use `replaceAll` in typescript and angular 10. 

But I get this error: **Property &#39;replaceAll&#39; does not exist on type &#39;string&#39;**.

This is my code:
```
let date=&quot;1399/06/08&quot;
console.log(date.replaceAll(&#39;/&#39;, &#39;_&#39;))
```
Output: 13990608

How can fix my typescript to show me this function?

Property &#39;replaceAll&#39; does not exist on type &#39;string&#39;

Using the jest-preset-angular to perform the unit test, but got an warning as `UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON` not sure what causing the error, due to this the application is stuck and not running the other unit test.

    PASS  src/app/pages/result/result-filter/result-filter.component.spec.ts (6.251 s)
     PASS  src/app/pages/result/search-navigation/search-navigation.component.spec.ts
     PASS  src/app/pages/result/filter-modal/filter-modal.component.spec.ts (5.699 s)
     PASS  src/app/app.component.spec.ts
     PASS  src/app/pages/test-type/test-type.component.spec.ts (12.857 s)
    (node:3280) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON
        --&gt; starting at object with constructor &#39;Object&#39;
        |     property &#39;element&#39; -&gt; object with constructor &#39;Object&#39;
        |     property &#39;componentProvider&#39; -&gt; object with constructor &#39;Object&#39;
        --- property &#39;parent&#39; closes the circle
        at stringify (&lt;anonymous&gt;)
        at writeChannelMessage (internal/child_process/serialization.js:117:20)
        at process.target._send (internal/child_process.js:808:17)
        at process.target.send (internal/child_process.js:706:19)
        at reportSuccess (/Users/macbook/Projects/Playtime Projects/IDP/Idp.Bx.Ui/idp/node_modules/jest-worker/build/workers/processChild.js:67:11)
    (Use `node --trace-warnings ...` to show where the warning was created)
    (node:3280) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
    (node:3280) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    (node:3281) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON
        --&gt; starting at object with constructor &#39;Object&#39;
        |     property &#39;element&#39; -&gt; object with constructor &#39;Object&#39;
        |     property &#39;componentProvider&#39; -&gt; object with constructor &#39;Object&#39;
        --- property &#39;parent&#39; closes the circle
        at stringify (&lt;anonymous&gt;)
        at writeChannelMessage (internal/child_process/serialization.js:117:20)
        at process.target._send (internal/child_process.js:808:17)
        at process.target.send (internal/child_process.js:706:19)
        at reportSuccess (/Users/macbook/Projects/Playtime Projects/IDP/Idp.Bx.Ui/idp/node_modules/jest-worker/build/workers/processChild.js:67:11)
    (Use `node --trace-warnings ...` to show where the warning was created)
    (node:3281) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
    (node:3281) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    (node:3279) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON
        --&gt; starting at object with constructor &#39;Object&#39;
        |     property &#39;element&#39; -&gt; object with constructor &#39;Object&#39;
        |     property &#39;componentProvider&#39; -&gt; object with constructor &#39;Object&#39;
        --- property &#39;parent&#39; closes the circle
        at stringify (&lt;anonymous&gt;)
        at writeChannelMessage (internal/child_process/serialization.js:117:20)
        at process.target._send (internal/child_process.js:808:17)
        at process.target.send (internal/child_process.js:706:19)
        at reportSuccess (/Users/macbook/Projects/Playtime Projects/IDP/Idp.Bx.Ui/idp/node_modules/jest-worker/build/workers/processChild.js:67:11)
    (Use `node --trace-warnings ...` to show where the warning was created)
    (node:3279) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
    (node:3279) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    
     RUNS  src/app/pages/location/location.component.spec.ts
     RUNS  src/app/pages/signup/signup.component.spec.ts
     RUNS  src/app/pages/login/login.component.spec.ts
    
    Test Suites: 10 passed, 10 of 20 total
    Tests:       16 passed, 16 total
    Snapshots:   1 obsolete, 5 passed, 5 total
    Time:        2180 s

I am not sure how to run the node --trace-warnings. Looks like it a serialization issue, even it is just a warning but not sure where is the issue. Is there any better way to find the exception

UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON with Jest + Angular

I have an Angular application that I am trying to debug in [VS Code][1].

When I compile and run the application (`ng serve`) the breakpoints are bound:

[![enter image description here][2]][2]

However, when I specify a different configuration e.g. `-c qa` or `-c uat` they are unbound:

[![enter image description here][3]][3]

 1. Why are the breakpoints unbound when I specify a different
    configuration? 
 1. How do I bind the breakpoints for a debug session targeting a particular environment?

---

#### Relevant information

##### *angular.json* sample environment configuration:


```
&quot;uat&quot;: {
  &quot;fileReplacements&quot;: [
    {
      &quot;replace&quot;: &quot;src/environments/environment.ts&quot;,
      &quot;with&quot;: &quot;src/environments/environment.uat.ts&quot;
    }
  ],
  &quot;optimization&quot;: true,
  &quot;outputHashing&quot;: &quot;all&quot;,
  &quot;sourceMap&quot;: false,
  &quot;extractCss&quot;: true,
  &quot;namedChunks&quot;: false,
  &quot;extractLicenses&quot;: false,
  &quot;vendorChunk&quot;: false,
  &quot;buildOptimizer&quot;: true,
  &quot;budgets&quot;: [
    {
      &quot;type&quot;: &quot;initial&quot;,
      &quot;maximumWarning&quot;: &quot;2mb&quot;,
      &quot;maximumError&quot;: &quot;5mb&quot;
    },
    {
      &quot;type&quot;: &quot;anyComponentStyle&quot;,
      &quot;maximumWarning&quot;: &quot;6kb&quot;,
      &quot;maximumError&quot;: &quot;10kb&quot;
    }
  ]
},
```

##### Software versioning:

- [Visual Studio Code][1] `1.50.1`
- [Chrome][4] `83.0.4103.122`
- [Debugger for Chrome][5] `4.12.11`
- [JavaScript Debugger (Nightly)][6] `2020.10.2217`


  [1]: https://code.visualstudio.com/
  [2]: https://i.stack.imgur.com/iON2a.png
  [3]: https://i.stack.imgur.com/tgPA3.png
  [4]: https://www.google.com/intl/en_uk/chrome/
  [5]: https://github.com/Microsoft/vscode-chrome-debug
  [6]: https://github.com/microsoft/vscode-js-debug

Content Type	Original Author	Original Content on Stackoverflow
Question	rrr	View Question on Stackoverflow
Solution 1 - Javascript	JSON Derulo	View Answer on Stackoverflow

Angular 10 Upgrade - Fix CommonJS or AMD dependencies can cause optimization bailouts

Javascript Problem Overview

Javascript Solutions

Solution 1 - Javascript

Replace with ES modulized library (recommended)

Whitelist CommonJS dependency

Skipping acquire of configured file 'main/binary-i386/Packages'

Is using malloc for int undefined behavior until C++20

Attributions