Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

evaluate import { m } from "./messages.js syntax #345

Open
samuelstroschein opened this issue Jan 26, 2025 — with Linear · 1 comment
Open

evaluate import { m } from "./messages.js syntax #345

samuelstroschein opened this issue Jan 26, 2025 — with Linear · 1 comment

Comments

Copy link
Member

Context

Paraglide lacks auto-imports of messages.

Paraglide's wildcard import import * as m is tree-shakable and leads to autocomplete once the wildcard import exists at the top of the file. But, VScode doesn't auto create the import when typing m.

Users are using workarounds to get auto-imports working #151. Apparently, tree-shaking is uneffected.

Proposal

Implement (and default) to import { m } from "./messages.js" if the workaround is tree-shakable for Paraglide V2.

Copy link
Member Author

Even better if it works with a default export. TBD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant