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
First of all, great work @Niels-IO
I am not sure why NextJS doesn't do this by default for static export.
Isn't the point of building your whole site locally to be able to optimise all the assets including images?
As for my bug report. I am using bun on my NextJS project.
This library works well until at the very last part when it doesn't exit automatically after running the post-build script: "next-image-export-optimizer"
I wish to include the static export on my CI build process, but since this is not exiting automatically, the CI simply times out even though it has successfully export the assets.
I have created repro using this fork, under the feat/bun branch:
First of all, great work @Niels-IO
I am not sure why NextJS doesn't do this by default for static export.
Isn't the point of building your whole site locally to be able to optimise all the assets including images?
As for my bug report. I am using bun on my NextJS project.
This library works well until at the very last part when it doesn't exit automatically after running the post-build script: "next-image-export-optimizer"
I wish to include the static export on my CI build process, but since this is not exiting automatically, the CI simply times out even though it has successfully export the assets.
I have created repro using this fork, under the
feat/bun
branch:https://github.com/arvilmena/fork--next-image-export-optimizer/tree/feat/bun
I hope you can take a look on this.
Thanks!
The text was updated successfully, but these errors were encountered: