luxdamore / nuxt-prune-html Goto Github PK

Hi!

We just apply the module to our website, but the function seems failed because of CloudFront CDN.
We notice that your website (https://www.fallimenti.it/) uses CloudFront CDN as well, and we like to know how did you setup your CDN settings to make it work?

The module is really a life-saver!
Thanks for advance!

Hello, I tested this plugin it's awesome but it doesn't seem to work with vue-lazyload. How do I make them work at the same time?

Is there any risk of using it, like black hat or any other thing?

How does google sees this practice?

Or is it a white hat?

Fix: standard-version also in the npm package

Related to: #4

Edit: NVM, I guess this is actually considered dynamic rendering and isn't a problem, so disregard

Describe the bug
When using the generate command of Nuxt (without static mode set) the generation fails with a Garbage Collection failure.

To Reproduce

• Setup a Nuxt Project with the nuxt-prune-html module
• Add a few pages
• Generate the website using yarn nuxt generate
  Expected behavior
  Generation is successful and pruning is applied

Screenshots

Additional context
I've tested it on my machine and when using Netlify build system.
Node version: 15.14.0

When i use the @luxdamore/nuxt-prune-html, https://web.dev/measure/ from Google say "Links are not crawlable" in SEO section with medium impact.

When i remove @luxdamore/nuxt-prune-html and test again, the alert not showing anymore.

How to avoid this message? Does this have an impact on SEO?

Hi!

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.

• Following this list of UAs, what if the default string was lighthouse|google page speed? Also, it was not directly clear that the lighthouseUserAgent was a (string that would compile to a) Regex value.

Describe the solution you'd like
A clear and concise description of what you want to happen.

• Maybe we could add in the docs that lighthouseUserAgent will be converted to a Regex and that, by default, it is case insensitive.

Describe the bug
I was using this module with my nuxt web app, it worked as expected. but since this month it doesn't prune the selectors in lighthouse which leads to a mediocre performance score

To Reproduce
Steps to reproduce the behavior:

1. use a custom script like gtm with a class="gtm"
2. config the nuxt-prune-html as follow:

  hideGenericMessagesInConsole: true
  hideErrorsInConsole: true
  selectors: [
    'script[class="gtm"]',
  ],
}

3. run npm run build && npm run start
4. run a lighthouse report

Nuxt version: 2.15.7

Expected behavior
the gtm script shouldn't be served when running a lighthouse report

Screenshots

Here's the config I setup for my nuxt app

export default {
  // Target: https://go.nuxtjs.dev/config-target
  target: 'static',
  ssr: true
}

and I add nuxt prune as indicated in the documentation

modules: ['@luxdamore/nuxt-prune-html'],

  pruneHtml: {
    enabled: true
  },

to test it, I just force enable to true. I use yarn generate and yarn serve to test it locally, but what it showing is just all white. Did I do something wrong about its implementation?

Hi! Can you explain queryParametersToExcludePrune logic?

I have added this property in nuxt.config.js. Then, I request page with ?prune=false. But it's looks like not working (same score like as pruned). Maybe I did something wrong? How I can check prune/unprune?

\duplicated