solidjs / solidjs/solid-vite-plugin
I updated `vite-plugin-solid` and now namespaces merged with components are no longer allowed
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 520
- Forks
- 70
- Avg merge
- 23h 35m
- Merged PRs (30d)
- 39
Description
Describe the bug
If I create a .tsx file with this content
function A() {
return <>1</>
}
namespace A {
export const a = 1;
}
console.log(A);
It throws this error when I load the page (Running vite dev)
Transform failed with 1 error:
ERROR: The symbol "A" has already been declared
I tried downgrading vite-plugin-solid and it worked
npm i vite-plugin-solid@2.8.0
(On the playground it always works)
Your Example Website or App
(localhost)
Steps to Reproduce the Bug or Issue
- Put a merged namespace declaration WITH A COMPONENT somewhere
- Run
vite dev - Go to the web page
Expected behavior
I expected this allowed TS syntax to not stop working
Screenshots or Videos
No response
Platform
- OS: Windows
- Browser: Edge
- Version: 120.0.2210.77
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provided .tsx example containing a component and merged namespace, then run vite dev to reproduce the transform error. Compare the behavior with vite-plugin-solid@2.8.0; done means the TypeScript syntax loads without the duplicate-symbol error in the current plugin version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vite
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100