Even migrating to Sveltekit 1.0 this video was very helpful. One thing I wanted to mention, when using the static adapter, it's probably best to use slug instead of uri when defining the link. Using uri will add a trailing slash after the slug, while slug will just return as is. So, if the user has javascript disabled, using uri instead of slug will send the user to a 404. Otherwise, you'll need to add `export const trailingSlash = 'always'` to +layout.js
Be interesting if you or someone could show an example of using the the new 'endpoint' method too as Brittney mentioned at the end... anyone lol?? Instead of the Context Module, the shadow endpoints or just endpoints (as it's being referred to now) is shown on the Docs but it would be awesome so see it here too as a 'real life' example of that.... thank you this was great!
Even migrating to Sveltekit 1.0 this video was very helpful. One thing I wanted to mention, when using the static adapter, it's probably best to use slug instead of uri when defining the link. Using uri will add a trailing slash after the slug, while slug will just return as is. So, if the user has javascript disabled, using uri instead of slug will send the user to a 404. Otherwise, you'll need to add `export const trailingSlash = 'always'` to +layout.js
Good to know, thanks! 👍
So happy that I found this channel. Good content
THANK YOU
Be interesting if you or someone could show an example of using the the new 'endpoint' method too as Brittney mentioned at the end... anyone lol?? Instead of the Context Module, the shadow endpoints or just endpoints (as it's being referred to now) is shown on the Docs but it would be awesome so see it here too as a 'real life' example of that.... thank you this was great!
What if WordPress use svelte internally instead of react.?
ᵖʳᵒᵐᵒˢᵐ ?
Code repo is here: github.com/brittneypostma/wp-blogpostma