You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a use case where I want to prerender a react app as part of a build pipeline for static deployment. I'm using parcel for the build step, which means I can't use e.g. prerender-spa-plugin. But your documentation made prerendering seem simple enough I was wondering - why not rig up a CLI script and run prerendering that way?
I'm not sure if this is the right place to tell you about this, but here's a proof of concept that works perfectly for my use case: https://github.com/Ezku/prerenderer-cli
In short, in my project I have a package.json like this:
Which yields parcel'd and prerender'd output in dist, the default output directory for parcel. I don't need to write any code in the project for this to happen because prerenderer-cli is quite enough.
What do you think? Is this interesting to you? Thanks for the great tool, I'm liking it a lot at this point.
Cheers,
Eevert
The text was updated successfully, but these errors were encountered:
Hi,
I have a use case where I want to prerender a react app as part of a build pipeline for static deployment. I'm using parcel for the build step, which means I can't use e.g.
prerender-spa-plugin
. But your documentation made prerendering seem simple enough I was wondering - why not rig up a CLI script and run prerendering that way?I'm not sure if this is the right place to tell you about this, but here's a proof of concept that works perfectly for my use case: https://github.com/Ezku/prerenderer-cli
In short, in my project I have a
package.json
like this:Which yields parcel'd and prerender'd output in
dist
, the default output directory for parcel. I don't need to write any code in the project for this to happen becauseprerenderer-cli
is quite enough.What do you think? Is this interesting to you? Thanks for the great tool, I'm liking it a lot at this point.
Cheers,
Eevert
The text was updated successfully, but these errors were encountered: