Generated inline styles are wrong

[cheesytim]

Hello! I have SPA (vue + vue cli), after build, I get styles from another page, my main page (/, -> redirect to /signin) contains only auth form, simple header, footer, logo (look at example of using styles in screenshot) and it can't pass you next page, until you Sign In

But, my generated inline styles are from protected page (for authorized users)
How is it happen?
Puppeteer can't auth on it own, but seems it get protected page for generated styles, can I control somehow generating process for watching Pupeteer work, console?(might be getting Promise in config?).

My vue.config.js

  configureWebpack: config => {
    if (process.env.NODE_ENV === 'production') {
      config.plugins.push(
        new HtmlCriticalWebpackPlugin({
          base: path.resolve(__dirname, 'dist'),
          src: 'index.html',
          dest: 'index.html',
          inline: true,
          minify: true,
          width: 1200,
          height: 900,
          ignore: ['@font-face'],
          penthouse: {
            blockJSRequests: false
          }
        })
      );
    }
  },

Any suggestions?

[thescientist13]

Thanks for reporting this issue @Tim152

I would see some other related open issues, it's not clear how well critical itself works with SPA, since all the HTML is generated dynamically.

• "css should not be empty" with postcss config in next.js with purge css #31
• How Critical Css with exact path="/" of the Reactjs #29
• Have HtmlCriticalWebpack contribute critical's changes back to the compilation #27 (potential solution, not sure how viable it actually is)

Can you confirm if running critical directly from the command line produces different (better / expected) results?

[cheesytim]

@thescientist13 Thank you for respond!
Unfortunately no, critical directly from command line produces exactly the same wrong result, seems like it's not plugin's fault..