#Is there a starter kit available for the latest beta? (v3.0.0-beta.103)

32 messages · Page 1 of 1 (latest)

mortal nexus
#

I find it extremely difficult / if not impossible to update a project from beta.65 to beta.103. A starter kit update or new npx create-payload-app@latest would help a lot

mortal nexus
#

Another way to ask is: how can I start a new project using the latest version - v3.0.0-beta.103? To all the dependencies and the right setup (importMap, etc.) - Then I can migrate my current code in that new foundation. Thks in advance

wooden dirge
#

I'd be interested in an answer here, too. I just did something similar (almost done) and the way I went about it was quite literally scrolling up through the release changelog and updating code whenever "breaking changes" were mentioned. Admittedly very tedious

mortal nexus
#

That's what I am doing now 🙂

#

Not error prone...

mortal nexus
#

Doesn't work

#

app/(payload)/layout.tsx is using import { RootLayout } from '@payloadcms/next/layouts' -> I added it as it was not present in package.json, but still it doesn't work

#

using Node v20.9.0

#

Amy help would be appreciated, would love to keep using v3 but I am starting to question it to be honest

grizzled stag
#

but yeah, we're in beta and things change

quartz onyx
#

do you guys want a starter app for the latest beta?

wooden dirge
#

that would be pretty pog yea

quartz onyx
#

let me upload one to github give me a moment

#

the build of the standalone still isn't working, but i did fix most of the stuff on their website template

quartz onyx
#

@wooden dirge can you pm i'll send you a link and you can test it to make sure it works ok

#

anyone else it wants it too let me know

mortal nexus
sleek mango
#

or "npx create-payload-app@beta"

quartz onyx
lavish bane
#

This is the real answer

#

select website template when asked

#

for most complete setup

quartz onyx
# lavish bane ^

For some reason that command installs beta 97, which then breaks since the code needs 103, also docker is broken on it, and some other things.. i just tried it again it still has the same issues

lavish bane
#

huh, that's interesting. To fix, you can hop into package.json and give all payload-xyz packages the same version tag

#

then nuke node modules and pnpm/yarn/bun i

quartz onyx
lavish bane
#

ye kinda weird. I remember using the npx thing a couple days ago to make repro for an issue I was having.

Prolly a temporary thing that got borked