search

nuxt-modules / og-image

Generate OG Images with Vue templates in Nuxt.
https://nuxtseo.com/og-image
360 stars 23 forks source link

Firebase deploy Failure on MacBook M1: Incorrect Platform Detection for @css-inline/css-inline-darwin-arm64 #170

Open harlan-zw opened 3 months ago

harlan-zw commented 3 months ago

https://github.com/unjs/nitro/issues/2096

bigrig2212 commented 3 months ago

Is there an alternative library that we can use instead of nuxt-og-image that will work with firebase?

taking it out of package.json and rebuilding pnpm-lock.yaml fixes the issue and allows a deploy, but then there are a bunch of 500 errors for screens that need it...

Note that error occurrs for libs other than @css-inline, such as @resvg

harlan-zw commented 3 months ago

This issue will be solved when the latest css-inline WASM is stable (see https://github.com/Stranger6667/css-inline/issues/341).

Not sure what else you mean, it should work on Firebase afaik

bigrig2212 commented 3 months ago

Not just the css-inline lib - and not just on M1s:

Screenshot 2024-03-18 at 9 15 05 PM

On

Screenshot 2024-03-18 at 9 16 04 PM

(Works fine running locally - just doesn't deploy to FB)

harlan-zw commented 3 months ago

The issue is that you built your npm locks binary dependencies with the assumption that it will be deployed on Mac (the default behavior).

You can try and solve by running npm install -f as a first step within Firebase, which will force re-install the binaries(maybe). You can also update the lock to remove the linking.

I'm guessing pnpm doesn't have this issue.

web-tailor commented 2 months ago

I have the same issue. Macbook pro (2015) Intel i5. Disabling ogImage in nuxtseo is what I have done to solve the deployment issue. However, it's a pity we cannot use ogImage because of this.

mfreeman451 commented 2 months ago

This issue will be solved when the latest css-inline WASM is stable (see Stranger6667/css-inline#341).

Not sure what else you mean, it should work on Firebase afaik

Seems like the issue was closed for the WASM thing.. whats the next step?