For a svelte package index.js group imports don't work anymore

[24jr]

Describe the bug

https://kit.svelte.dev/docs/packaging#publishing

This used to work before update a few weeks ago and stopped and still doesnt work

import { Foo } from 'your-library';

but this does

import Foo from 'your-library/Foo.svelte';

but easier to use first syntax for multiple imports

Don't believe much of anything changed except updating so I think the issue has to do with something in an update

Reproduction

make svelte package

npm run package
publish ./package --access public

import into another sveltekit project

Logs

No response

System Info

Latest svelte

Severity

annoyance

Additional Information

Alternative is fine but at some point would be nice

[24jr]

this may have to do with other issue I am having #3473

[ignatiusmb]

Please see #2263 (comment) or follow the issue template and provide a proper reproduction.

[24jr]

@ignatiusmb That link just shows u telling someone the basic usage of this which I had already done and as I said worked fine until updating to newer version but sure just close the issue. That solves the problem right...And if there is some issue with how I presented this enlighten me but bringing up the issue poorly to your standard is better than not bringing it up at all

[ignatiusmb]

From the issue template:

A link to a repository, or a fork of https://node.new/sveltekit, that reproduces the issue. Explaining how to reproduce is generally not enough. It pushes the burden of creating a reproduction project onto a small set of volunteer maintainers and isn't scalable. If no reproduction is provided, the issue will be closed.

[24jr]

@ignatiusmb Ok well you are right that I am not setting up all that for someone and it would require whoever fixes these things to make an nmp package and idk how I make that easy for them and also don't desire to spend that much time doing all that as I am busy so if simply bringing up the valid issue without all that isnt good enough then I understand and will wait until one day someone else finds the problem and desires to create issue to your standard. I guess its a tradeoff of work to issue fixer or issue creator and you are right I am putting more on the fixer but thats just where I'm at