From 0b01952320f0e4883f65641e94892ef71b675c28 Mon Sep 17 00:00:00 2001 From: Carsten Kragelund Date: Fri, 28 Jul 2023 13:50:15 +0200 Subject: [PATCH] docs: more notes --- NOTES.org | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/NOTES.org b/NOTES.org index f622e4e..721d1d4 100644 --- a/NOTES.org +++ b/NOTES.org @@ -1,3 +1,19 @@ * Not using App Router -* Doesn't register rapid run as a script in the package.json +It by default uses the Pages Router, though it was fairly simple to just create app/layout.tsx and move over pages/index.tsx to app/page.tsx and move the getServerSideProps into the component function body + +* Doesn't register =rapid run= as a script in the package.json +I have to manually run =rapid run= rather than having all the commands as actions with npm as a task runner + * Have to run both =rapid run= and =next dev= to start the app +After bootsrapping, just running npm run dev only starts the nextjs and I have to manually run rapid run seperately, and conversely running rapid run only starts the backend, I would expect that it "just works" + +* =rapid new= gotcha +Just running =rapid new = doesn't work, I expected it to behave like =cargo new=, where you pass the app name when invoking the cli +Though that might just be my Rust brain, and this is more common with JS tools + +* Defaults to remix.run +=rapid new= by default just uses remix, I would have assumed it would at prompt for which framework you'd like to use since it supports both remix and next + +* =rapid run= seems to recompile too often +Even when changing a non-backend file, rapid run will rebuild the entire backend/regenerate the types. This is not really a problem as its extremely fast, but it does mean the console updates with the build information even for non-backend changes. +This includes documentation files too like this =NOTES.org= or the =README.md=