-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Cannot call .tap() on a plugin that has not yet been defined. Call plugin('html').use(<Plugin>) first. #187
Comments
this repo needs love.. vue pre-rendering is lacking so much support. |
@ricky11 I know. I'm focusing on Python right now so I can't help much with investigating the problem / contributing. :( I totally wish I have a time-turner and I would! I settled right now with not pre-rendering my hobby project which is very small. Another workaround if you really, absolutely need pre-rendering is using Nuxt. But that could be overkill. 🙈 |
Thanks for replying. Yes nuxt is indeed overkill. I wonder what nuxt does under the hood for pre rendering. Nevertheless, your module works well for our home page, but for my blog it doesn't even though i have added that route. I am using a cms (prismic) to fetch the data, and i assumed that headless chrome would render the page wait for the data to fetch and then save the blog page staticly.. but it seems like it doesn't.. maybe its a timeout issue? its sad to see the vue core team dont support pre-rendering, as even Chris Fritz has mostly left the team and given up maintaining his package. It almost seems vue is forcing us to use nuxt, but most of it isn't needed if we maintain our own routes and dont need SSR. Thanks so much however for this package, if you have the time, please let me know if there are other options, (react-snap?) oh by the way if in future i decide to uninstall the package and revert the changes made to vue.config.js and my main.js how would i do that? i tried to do it some time ago and my package broke.. Thanks |
I'm not a maintainer or contributor of this package. I am a fellow user who would also like to pre-render a few routes. Unfortunately, I can't think of other options right now, sorry. 😔
Apr 26, 2021, 09:34 by ***@***.***:
…
Thanks for replying. Yes nuxt is indeed overkill. I wonder what nuxt does under the hood for pre rendering.
Im also looking at gridsome, but again i would need to make so many changes to an existing production app only to pre render 2 or 3 routes.
Nevertheless, your module works well for our home page, but for my blog it doesn't even though i have added that route. I am using a cms (prismic) to fetch the data, and i assumed that headless chrome would render the page wait for the data to fetch and then save the blog page staticly.. but it seems like it doesn't.. maybe its a timeout issue?
its sad to see the vue core team dont support pre-rendering, as even Chris Fritz has mostly left the team and given up maintaining his package. It almost seems vue is forcing us to use nuxt, but most of it isn't needed if we maintain our own routes and dont need SSR.
Thanks so much however for this package, if you have the time, please let me know if there are other options, (react-snap?)
Thanks
Rishi
—
You are receiving this because you authored the thread.
Reply to this email directly, > view it on GitHub <#187 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/ADIDWNXZKKATBH6DF3KGD7DTKWIZ3ANCNFSM4ZVZDFFA>> .
|
Oh thats okay... it seems there are other people looking for a maintained pre-render package... im going to look in to react-snap which also works with vue.. now if only i could uninstall this without breaking vue cli! |
try this: const html = require('html-webpack-plugin') |
Describe the bug
After following instructions in README.md, running
npm run build
gives error:Cannot call .tap() on a plugin that has not yet been defined. Call plugin('html').use(<Plugin>) first.
To Reproduce
Steps to reproduce the behavior:
npm run build
Expected behavior
Project builds succesfully 🎉
Screenshots
Additional context
Package version:
Vue version:
Vue CLI version:
-> % vue --version @vue/cli 4.5.11
The text was updated successfully, but these errors were encountered: