Ben McCann

I'm not sure it should reflect `command`. E.g. I think you should be able to test serving in production mode. If you want to know what command was run then...

This won't really work with SvelteKit. We have a [`trailingSlash` option](https://kit.svelte.dev/docs/configuration#trailingslash) which indicates whether we expect URLs to have a trailing slash or not. This PR is currently assuming that...

SvelteKit historically hasn't used the `publicDir` and `base` options, but does its own static asset serving. I put together a branch to use Vite's implementation. I came across this PR...

There are official docs now: https://kit.svelte.dev/docs

@feross I thought I'd check in on this. I'm happy to take another approach if you have some thoughts. Thanks!

@feross any thoughts on how we might best be able to support ESM?

>Are ESM-only packages supported by browserify? Would you even need to use Browserify at that point? ESM packages are natively supported in the browser. I have seen some posts suggesting...

You could also support ESM by adding a wrapper which wouldn't require using Rollup or Microbundle: https://nodejs.org/api/packages.html#packages_approach_1_use_an_es_module_wrapper If we can go ESM-only that'd still be preferable for reduced complexity, but...

I guess by "lib for source", you mean `svelte-kit package`? I was only thinking of the docs site, since that was the one place I'd seen Sapper being used Do...

> I notice a bit of jank when navigating the pages – whatever might be causing that. There's some issues in dev mode that might cause a flash of unstyled...