Tyler Cote

> This will casue the page blinking.How did you solve it? The page blink seems to be because of the rapid change in the elements height, I think disabling it...

+1

For reference, here is my current polyfill instructions for my package: ### Crypto-browserify ``` BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default. This...

As well as my commonJS list that I'm using for angular: ```js "allowedCommonJsDependencies": [ "it-concat", "crypto", "debug", "libp2p", "libp2p-gossipsub/src/utils", "@chainsafe/libp2p-noise/dist/src/noise", "libp2p-bootstrap", "libp2p-websockets", "libp2p-websockets/src/filters", "multiaddr", "peer-id", "ecies-geth", "secp256k1", "libp2p-gossipsub", "hashconnect" ],...

@elalish yeah they dont like the URL being in there at all

I got around it by building it locally and just bundling this lottieloader with it, but I would prefer not having to do that each time it updates lol

Is this really the final solution? Having to build it myself for each update?

I removed the reference to the remote hosted code and bundled it with it, the issue is the default link to the remote hosted code

[Here is my extension](https://chromewebstore.google.com/detail/hashpack/gjagmgiddbbciopjhllkdnddhcglnemk) And here is the response I got from support: 

I believe I tried that yes, its all minified and obfuscated and just having that external URL in there was a red flag