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
When doing function splitting with only app router component on lambda, this issue can happen.
This file is included for every app router route/component, including _app and _document, which are bundled everywhere except on app router only splitted function. (it should not be included btw)
The import is done before the setNodeEnv function call on lambda and so NODE_ENV is undefined and react try to load the dev stuff.
FIX
There is a very easy fix for those running into this set the NODE_ENV env variable to production.
This should also be done on sst by default
The text was updated successfully, but these errors were encountered:
When doing function splitting with only app router component on lambda, this issue can happen.
This file is included for every app router route/component, including
_app
and_document
, which are bundled everywhere except on app router only splitted function. (it should not be included btw)The import is done before the
setNodeEnv
function call on lambda and so NODE_ENV is undefined and react try to load the dev stuff.FIX
There is a very easy fix for those running into this set the
NODE_ENV
env variable toproduction
.This should also be done on sst by default
The text was updated successfully, but these errors were encountered: