Import {type Foo} Improperly handled (?)

[Caesarovich]

Hi,
This snippet results in Vinxi bundling the db package even if only the types are imported:

import { type Staff, type UserStatus } from 'db/schemas';

This caused me some issues. The 'fix' is to write it this way:

import type { Staff, UserStatus } from 'db/schemas';

Now Vinxi appropriately ignores this package during bundling. I'm unsure if this is a bug or desired because as @Brendonovich mentionned on Discord:

"[this could be because of] ...the assumption there may be side effects you care about"<

If that's intended then this issue might help someone having the same issue as me in the future.

[LexSwed]

It might be fine to keep this behaviour if we had an easy way to scream at the browser when something we really don't want there gets bundled, like server-only, but with use server annotation that is already in place?

[Brendonovich]

@LexSwed you can get the same effect as server-only by adding this in your files

import { isServer } from "solid-js/web";

if(!isServer)
  throw new Error("This module cannot be imported in the browser")

[LexSwed]

That would work, but I mean that I already marked a file as server-only, it should automagically make anything up the dependency tree not includable in the client bundle.