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
We are using 3.28.1 because we are on the latest even numbered Node version (AWS restriction), and these dependency issues are causing some problems. A recent update seemed to have made some peer dependencies to require us to use [email protected], (@payloadcms/[email protected], @payloadcms/[email protected], @payloadcms/[email protected] for example) but not all (@payloadcms/db-mongodb@^3.28.1 still requires 3.28.1).
[email protected] requires a later version of node than what AWS allows so we are sort of stuck.
Anyone else using an older version of Payload experiencing this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are using 3.28.1 because we are on the latest even numbered Node version (AWS restriction), and these dependency issues are causing some problems. A recent update seemed to have made some peer dependencies to require us to use [email protected], (@payloadcms/[email protected], @payloadcms/[email protected], @payloadcms/[email protected] for example) but not all (@payloadcms/db-mongodb@^3.28.1 still requires 3.28.1).
[email protected] requires a later version of node than what AWS allows so we are sort of stuck.
Anyone else using an older version of Payload experiencing this?
Beta Was this translation helpful? Give feedback.
All reactions