R.A. Ray

I had a similar issue (https://github.com/shubhamjain/svg-loader/issues/30) that was resolved by moving the dependency from `dev` to normal dependencies. This project uses Yarn and has no such distinction

@shubhamjain Hmm. I'm still getting this error: ``` external-svg-loader@npm:1.6.8 couldn't be built successfully (exit code 1 ... ``` It installs successfully after forcing it back to `1.6.1`.

@shubhamjain It doesn't. I tried the above as well as blowing away my entire cache and lock file. Here's the contents of the log file: ``` # This file contains...

> This repository holds the sources for Yarn 1.x (latest version at the time of this writing being 1.22). New releases (at this time the 3.2.3, although we're currently working...

@khalwat I am trying to get any result that makes sense. As part of that effort, I tried multiple URLs including the one shown in the example docs. > I've...

Yes. I know. I've tried that. I always get the result above regardless of the URL I enter.

The current config is this: ``` PluginCritical({ criticalUrl: '[production url]', criticalBase: 'craft/web/assets/dist', criticalPages: [ { uri: '', template: 'index' }, ], criticalConfig: { user: '[production user]', pass: '[production pass]', strict:...

I will try that, but I used multiple URLs that don't have passwords. Shouldn't I get a result from your website, or `https://google.com` which I also tried?

I removed the password. No change. I'm highly confused by your responses. Does Critical compare the scraped CSS against something else to generate its results?

I see, thanks. That was a clue. I switched everything to the staging environment which is a closer match to what I'm working with and it does seem to be...