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 had a problem deploying to Now 2.0 and I believe the root cause is in ncc and the way files are bundled together in the @now/node builder.
I was originally using a ternary operator to decide which file to dynamically read from the filesystem, but this always gave me the ENOENT: no such file or directory after deploying even though it worked fine on my machine.
After reading #216 I decided to see if changing the code would solve the problem and it worked! See the commit below for the fix.
This seems like it would be easy for users (like myself) to hit this bug and just give up. So it would be wonderful if this type of dynamic file reading could work with Now 2.0 😄
(forgive me if this is a duplicate bug)
The text was updated successfully, but these errors were encountered:
Hello again 👋
I had a problem deploying to Now 2.0 and I believe the root cause is in
ncc
and the way files are bundled together in the@now/node
builder.I was originally using a ternary operator to decide which file to dynamically read from the filesystem, but this always gave me the
ENOENT: no such file or directory
after deploying even though it worked fine on my machine.After reading #216 I decided to see if changing the code would solve the problem and it worked! See the commit below for the fix.
vercel/og-image@ed2fd9c
This seems like it would be easy for users (like myself) to hit this bug and just give up. So it would be wonderful if this type of dynamic file reading could work with Now 2.0 😄
(forgive me if this is a duplicate bug)
The text was updated successfully, but these errors were encountered: