What npm reports as the latest version of SvelteKit and adapter-node

[nstuyvesant]

Describe the problem

When typing npm outdated in a SvelteKit project,

npm reports the latest version of @sveltejs/kit and @sveltejs/adapter-node as 1.0.0-next.1 and 1.0.0-next.0 respectively.

My assumption is this is because there is not yet a 1.0 version.

Describe the proposed solution

As SvelteKit is not yet released but getting close, would it make sense to make the latest version equate to the latest next (1.0.0-next.137 and 1.0.0-next.35 at the time of this writing)? Then whenever someone does an npm outdated, they won't get @sveltejs/adapter-node and @sveltejs/kit in the list if they're really up-to-date.

Alternatives considered

Not change anything.

Importance

nice to have

Additional Information

No response

[benmccann]

Duplicate of #686