Sean Alunni

Results 13 comments of Sean Alunni

Due to [this](https://github.com/solidjs/vite-plugin-solid/issues/145) I use version 2.8.3 of `vite-plugin-solid`, but today I created a new project with the newest version by running `npm init solid` and I can confirm this...

I was talking about normal solid, solid start has still this problem

Isn't it possible to use `var`? ```js var A = () => { }; var A; (function (A) { A.hello = 'world'; })(A || (A = {})); ```

Do you transform the function to make HMR work BEFORE or AFTER transpiling typescript? Because if you were to do it after you could declare the function with `var` ```js...

> I'm not sure I understood the suggestion Don't worry, if the transformation must happen at the TypeScript level, the suggestion doesn't apply anyway

Isn't it possible to change ```ts export var A = _$$component(_REGISTRY, "A", function A() { // ... }, { location: "..." }); ``` Into ```ts import { createComponent } from...

TypeScript is not to blame this time in my opinion, because functions have always behaved differently from lambdas, It is the plugin's responsability to ensure that if I write a...

> A lot of Solid libraries I realized recently aren't built properly for SSR I'm having the same issue, can someone expand on what does it means practically to properly...

I don't think there is a need to use a weak map, you just need to exclude `Symbol(solid-proxy)` from the result of `ProxyHandler.ownKeys()`, `ProxyHandler.getOwnPropertyDescriptor()`, etc...

In this case you could put the hidden properties on the `ProxyHandler`: ```js const handler = { get(t, k) { return k === "c" ? this.data : t[k]; } };...