I’ve noticed the GitHub repo seems to be months behind what’s actually published to npm. For example, @plasmicapp/loader-nextjs@2.0.0-alpha.1 is on npm but the code isn’t on GitHub - the last commits to that package are from like 7 months ago.
I’m confused because Plasmic is supposed to be open source, but it’s hard to actually see the code or contribute when development isn’t happening in the open. Makes it pretty tough to test alphas or understand what’s changing too.
Is there a different branch I should be looking at, or is this just how you guys do releases? Would be cool to see the 2.0 App Router work and be able to provide feedback before things are finalized.
Hi @wytze_sligting, the latest commits to @plasmicapp/loader are indeed in our internal repo. We sync the internal main branch with the open source repo every time a PR is merged, but don’t currently have a process for sharing feature/alpha branches. This can be improved, we just haven’t had time for it yet.
Regarding the new app router/data query stuff, it is mostly testable now and not reliant on loader v2! I’m working through an example now, which will be ready soon. If you’d like, you can in theory test things with the project in /plasmicpkgs-dev/ now (the important stuff is mostly in plasmicpkgs-dev/app/[[…catchall]]/page.tsx)
You should be able to test the new data queries & hostless functions by appending &serverQueries=true to your project in Plasmic.
Thanks! That’s helpful to know about the &serverQueries=true flag - I’ll give it a try.
Quick question though - if the app router stuff works without @plasmicapp/loader-nextjs v2, what’s actually in the 2.0 alpha? I assumed that was the main driver for the major version bump. Just trying to understand what I should be waiting for vs what’s already usable.
Originally it was going to be part of the version bump, but we didn’t end up needing to break public APIs. 2.0 is now mainly removing deprecated APIs and bumping/supporting new dependency major versions (like React).
1 Like