slim (jamesc)
Second component instantiation has no owner when under vinxi start in a npm linked component
Here is a summary, hope that helps explain things (until it is out of date). Notably: if I had ran into a simple check
if(globalThis.createSignal && globalThis.createSignal !== createSignal) { console.error('ERROR, two solid-js versions detected');} else globalThis.createSignal = createSignal, it would have saved me a lot of confusion. https://github.com/nksaraf/vinxi/issues/473#issuecomment-274794971412 replies
Second component instantiation has no owner when under vinxi start in a npm linked component
The difference is between pnpm picked up rollup 4.37.0 and npm picked up rollup 4.36.0. If I override to rollup 4.37.0 in the root package I can use npm and it works. The next issue is, my packages are in ../cmp not ./cmp and it breaks again! Arrr.. I guess I have to figure out how to explain this to rollup..
12 replies
Second component instantiation has no owner when under vinxi start in a npm linked component
It is working for me to. I have a package-lock.json at stackblitz and I ran it several times in a chromium Cognito window and saw the error. Not sure if re-saving changing things, but I did not re-save anything. But now it works, not in my project, but only at stackblitz. I know for sure I do not have an alter ego! Ok, thanks for checking. My actual project is linking to packages where
type: module.12 replies
vxini seems to be packaging and shipping all server code to the client
Just for clearity: the build is way better at bundling so I'm not getting large page loads at all. It is just the dev environment that works differently. It was just alarming to see this in dev until I figured this out. I'm hoping to use those dev warnings to help me organize the code more, but I'm not so concerned about larger perhaps cached loads during dev.
40 replies
vxini seems to be packaging and shipping all server code to the client
The dev environment does rule out unreferenced imports. I did see that working. But, it does NOT look into any function(s) using that import to see if the function is also unreferenced; it just does a light scan. So, if the "use server" code was moved and there are no non-"use server" functions referencing that import, then it should work. In my case, I'm in
middleware.ts which should probably be assumed to be all server-code (not needing "use server"), but does not seem to be the case: I can comment out a key function call in a onRequest handler to a "use server" function in another file and I can get warning about "node:crypto" go away.40 replies
vxini seems to be packaging and shipping all server code to the client
Shouldn't "use server" work instead to tell the bundler that it is not responsible for importing? I have it issolated to one function call into another class that has "use server" in the destination function. I was hoping that "use server" would stop the "transforming" process from processing that file and generating warnings. I still see the warnings though.
40 replies
declare types for locals?
For me VSCodium [code] does not find my own RequestEventLocals. I have made many "guesses." F12 on event.locals takes me to
@solidjs/start/dist/server/types.d.ts, but F12 on event.locals.myVar it takes me to @solidjs/start/env.d.ts where that definition allows any string [key: string | symbol]: any; even though I have myVar defined just like you have user defined above.. Maybe having the declaration in entry-server works for the build, but I'm not sure how that will work for the editor at the same time; that does not seam like an entry point that VSCodium can pick up on. I tried various things using tsconfig.ts but I'm just not having any luck, there is a lack of clarity in the ts docs and lack of feedback from the tools. Here is how vite does it: https://vite.dev/guide/env-and-mode#intellisense-for-typescript .. That does work in VSCodium. They direct the end-user to create vite-env.d.ts which has /// <reference types="vite/client" /> at the top. I do not see any special code to load vite-env.d.ts in their github repo. Maybe VSCodium scans ./src for *.d.ts files? I do have "include": ["src"] and compilerOptions.types: ['src/global'] in my tsconfig.js (I guess one of those helps). If that is the case then the declare above should work; but it does not. Maybe solid's [key: string | symbol]: any; is interfering and capturing the search before it gets to the custom types? I'm pretty sure this works for everyone else but me .. lol8 replies
vxini seems to be packaging and shipping all server code to the client
Yes, when I started and 0.3.11,
createServerData$(()=> {/*server code*/}) worked.. Looks like the shortened the name. I simply replaced those with a server function passed to createResource so it would all work the same. Without looking under the hood, it does not seam to change any dependancies on the imports. I wonder if Ryan came up with something generic to handle things but, since generic may fall short, this changed.40 replies
vxini seems to be packaging and shipping all server code to the client
What do you mean by module? I have linked libraries that are used by other server processes but have code (like runtime type checking) that is imported and needed on the client as well.
40 replies