It's been a long time since I got excited about a framework. I often advocate for reinventing the wheel, how come I'm writing an ode to a framework...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for the great post 👍 The SvelteKit approach looks really neat.
A Svelte-noob question about the folder structure: why some files are in
src/..., some insrc/lib/..., some insrc/routes/...` (incl. the form component) and some in the root? Is it intentional and reflects some common practices in Svelte, or it's just for the showcase purposes?Thank you) Svelte kit uses file names as route paths, therefore all the routes need to be in the
src/routesfolder. E.g. if you would like to render a page/blog/some-nice-titleyou would create a/src/routes/blog/some-nice-title.svelte. Same goes for the.ts( or js) files with method handlers exported.And the lib folder is conveniently aliased to avoid imports from
../../../../../src/lib/file.ts, so that you could simply import$lib/file.tsHope that helps:-)
Cool, very neat 🔥
Nice job with the article. Trying to figure out how to make getSession() in hooks.ts useful. It only appears to fire once when I launch the dev server loading the home page. github.com/nstuyvesant/sveltekit-a....
TL; DR; This is the correct behaviour. Write to client session storage whenever it changes.
As per documentation,
getSessionruns only when the page is rendered on the server. If this initial state is changing on the front-end you need to make sure the changes are reflected in the store.To quote the docs once again:
While my SPA has several pages in /src/routes, only /src/routes/index.svelte appears to trigger getSession() in hooks (guessing it's because client side routing has taken over). If it's a user's first visit to the site (no session id in a cookie to lookup in handle() so request.locals.user doesn't get populated), getSession() doesn't seem to have much value.
What I've been doing in my /login endpoint (github.com/nstuyvesant/sveltekit-a...) is putting the user in the body of the endpoint response then doing a
session.set({ user: fromEndpoint.user })on the client in the login() method that called the endpoint.As all the examples of authentication using SvelteKit made use of getSession(), I thought I was doing something wrong.
I´m getting a error at line:
if (typeof req.body == 'string' || Array.isArray(req.body))
Property 'body' does not exist on type 'RequestEvent<{ db: DB; }, Partial<{ email: string; password: string; "repeat-password": string; }>>'.
Please, how to fix it ?
In the article I've used type
RequestHandler, your version seems to be usingRequestEvent. Is it a typo or the original type is no longer available for import?I copied the text as you wrote it using RequestHandler but something is changing in the compilation for RequestEvent. I believe it's the sveltekit version, I'm using the most current one.
I believe you're right and it seems that the way routes are defined has been changed since I wrote the article. Please take a look at svelte kit docs while I'm updating examples to the current version.
@blancout I've updated the article to reflect API of latest version, thank you for letting me know!
You´re wonderful !
One typo that tripped me up and might cause problems for others:
That should be "src/routes/signup.svelte", not signup.ts.
Otherwise, excellent post! Thank you!
Oops! Fixed it, thank you!
Glad you liked it!
Hi there, I am trying to follow along with this for practice and coming into the bug where I cannot get the data from req.locals.db when trying to save to the DB was there a work around for this? I am new to this so I have been un able to find a proper work around myself
Ignore me I think I sorted it =]