#Is there a starter kit available for the latest beta? (v3.0.0-beta.103)
32 messages · Page 1 of 1 (latest)
Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:
Documentation:
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
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
I started from this code as it's the latest update: https://github.com/payloadcms/payload/tree/beta/examples/custom-components
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
you can replace the entire (payload) folder with the latest version from the website template, then run npm payload generate:importMap
but yeah, we're in beta and things change
do you guys want a starter app for the latest beta?
that would be pretty pog yea
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
@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
I would love to test it as well if you don't mind 😉
or "npx create-payload-app@beta"
alot doesn't work with the default apps, but i think i resolved all my issues
^
This is the real answer
select website template when asked
for most complete setup
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
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
ya like i said i fixed it, and fixed docker last night as well, and i think i fixed some tailwind stuff, but out of the box they definitely don't work which is why i think others have been having issues
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