Closed jrhizor closed 1 year ago
I saw this a few days ago... I will try to have the fix during the next few days.
Thanks for reporting!
I saw this a few days ago... I will try to have the fix during the next few days.
Thanks for reporting!
Having the same issue going from 13.5.4 to 13.5.5, thank you for looking into it! :)
Published as next-plausible@3.11.2
.
Thanks!
Would it be possible to add a tag and a CHANGELOG entry?
I saw an update via Renovate bot but it took a bit of time to figure out what it was.
Thanks for this lib @4lejandrito 🙌
Would it be possible to add a tag and a CHANGELOG entry?
* https://github.com/4lejandrito/next-plausible/tags * https://github.com/4lejandrito/next-plausible/blob/master/CHANGELOG.md
I saw an update via Renovate bot but it took a bit of time to figure out what it was.
Thanks for this lib @4lejandrito 🙌
https://github.com/4lejandrito/next-plausible/commit/4482cb2eefba20737cd541a13b5fc0dd7dd4f0e7.
When running
next build
on 13.5.3 I don't see any warnings, but after upgrading to 13.5.5 I see:I'm using a pretty basic
next.config.js
:This is with
next-plausible@3.11.1
.I don't think this breaks anything, it's just a bit noisy in build logs.