[chore] export App types

[benmccann]

I think that exporting App will be enough to use init and request, but if not we can tweak a bit further

NOTE: If you open adapter-node/src/server.js in master, the import @sveltejs/kit/node cannot be resolved. I don't understand why. It'd be nice to use these new types in our own adapters, but I can't figure out why they're not available

[changeset-bot]

🦋 Changeset detected

Latest commit: 72cfa5f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@sveltejs/kit	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[jthegedus]

NOTE: If you open adapter-node/src/server.js in master, the import @sveltejs/kit/node cannot be resolved. I don't understand why. It'd be nice to use these new types in our own adapters, but I can't figure out why they're not available

In VSCode,@sveltejs/kit when 'clicked to follow' takes me to @sveltejs/kit/types/index.d.ts

With @sveltejs/kit/node I guess VSCode is looking for @sveltejs/kit/types/node but cannot find anything. There is a @sveltejs/kit/dist/node.js file which is what is meant to be imported but there's no associated .d.ts, just JSDocs.

Esbuild doesn't seem to have a problem resolving @sveltejs/kit/node during build.

[jthegedus]

The init type needs updating, or all the adapters. It requires 1 param, but currently each adapter calls init without a param.

Maybe this is the wrong init type, is there another?

kit/packages/adapter-vercel/files/entry.js

Line 6 in de736f9

init();

kit/packages/adapter-node/src/index.js

Line 6 in de736f9

init();

kit/packages/adapter-netlify/files/entry.js

Line 4 in de736f9

init();

[benmccann]

Thanks for taking a look! You're right - that parameter needed to be optional

As for my issue using @sveltejs/kit/node it seems to be because TypeScript lacks support for exports: microsoft/TypeScript#33079. I'll look at some of the workarounds on that thread