Eric Posts - Answer Overflow

Eric

•Created by Eric on 1/21/2025 in #support

[astro-island] Error hydrating /src/components/SignUp/SignUpForm.tsx TypeError: conds[i] is undefine

How do I debug an error like this? The SignUpForm is an astro island with client-load (no difference when using client-only though)

2 replies

SSolidJS

•Created by Eric on 12/1/2024 in #support

Solid Start Navigation

Hi, I've got a Solid Start page, and want to navigate to a different page within a component. I basically do the following:

const navigate = useNavigate();
navigate(`/${params.provider}/${params.mensa}/${nextDateString}`, { replace: true })

const navigate = useNavigate();
navigate(`/${params.provider}/${params.mensa}/${nextDateString}`, { replace: true })

I have also tried not passing replace: true, doesnt change anything though. The issue I have is this: The URL changes, as well as the history. But the page content doesn't change, only when I refresh the page. I guess this has something to do with navigating to the same page essentially, just with different params. What's the correct way of handeling a navigation like this? Thanks! I dont really think it's necessary, but this is what my [provider]/[mensa]/[date].tsx looks like

export default function Home() {
  const params = useParams()
  // Parse Date from format: "DD-MM-YYYY"
  function parseDate(date: string): string {
    const [day, month, year] = date.split('-')
    // '2024-10-10 22:00:00+00'

    return `${year}-${month}-${day}`
  }
  const date = parseDate(params.date)
  const servings = createAsync(
    async () => getServings(params.mensa, date, 'de'),
    { deferStream: true },
  )

  const mensa = createAsync(() => getMensa(params.mensa), {
    deferStream: true,
  })

  return ...
}

export default function Home() {
  const params = useParams()
  // Parse Date from format: "DD-MM-YYYY"
  function parseDate(date: string): string {
    const [day, month, year] = date.split('-')
    // '2024-10-10 22:00:00+00'

    return `${year}-${month}-${day}`
  }
  const date = parseDate(params.date)
  const servings = createAsync(
    async () => getServings(params.mensa, date, 'de'),
    { deferStream: true },
  )

  const mensa = createAsync(() => getMensa(params.mensa), {
    deferStream: true,
  })

  return ...
}

6 replies

SSolidJS

•Created by Eric on 11/21/2023 in #support

Generating Client Only code for static deployment

Hey people, I’m trying to build my solid start app for client use only. We’ve got an ordinary, no bells and whistles, webspace. And my goal is to deploy the solid start app to there. However, I’m not quite sure how to do that. Both when building with the default adapter and SSR turned off, and with the solid-start-static adapter, I only get "server" code. Also, it confuses me that SSR needs to be turned on for solid start static? I guess that makes sense because it needs to be rendered on the server in order to generate the static files. I don’t even know if I need a static export? There is quite a lot of code expected to run at runtime, and not a lot of static elements. Btw, it was already surprisingly difficult to figure out there even is solid-start-static, and 2) to find it, as in the docs it’s only referred to as »Static Hosting« Do you guys have recommendations on what to do?

16 replies

SSolidJS

•Created by Eric on 9/20/2023 in #support

Async TRPC query with ssr

2 replies

SSolidJS

•Created by Eric on 9/17/2023 in #support

Solid Start not deploying on vercel in turborepo

Hi all, my solid start project doesn't deploy to vercel, aka every build fails. There are no error's though, the build fails, because the deployment duration takes over 45 minutes. There are 0 errors in the output log, and the output ends with the following

backend:build:  solid-start build 
backend:build:  version  0.2.32
backend:build:  adapter  vercel
backend:build: 
backend:build: solid-start building client...
backend:build: solid-start rendering index.html...

backend:build:  solid-start build 
backend:build:  version  0.2.32
backend:build:  adapter  vercel
backend:build: 
backend:build: solid-start building client...
backend:build: solid-start rendering index.html...

3 replies

SSolidJS

•Created by Eric on 8/18/2023 in #support

SSR in Turbo Repo

Hi you all, I've recently converted 2 solid start projects of mine in a single turborepo Since doint that, I'm not able to use SSR anymore. No matter on what page I navigate, I'm prompted with this error: An error occured while server rendering /:

    
Unknown file extension ".ts" for ...\node_modules\.pnpm\[email protected]_@[email protected]_@[email protected][email protected]_solid-start-node_5s2kio276uhd5touku4ijt66hm\node_modules\solid-start\server\server.ts

TypeError: Unknown file extension ".ts" for ...\node_modules\.pnpm\[email protected]_@[email protected]_@[email protected][email protected]_solid-start-node_5s2kio276uhd5touku4ijt66hm\node_modules\solid-start\server\server.ts
    at new NodeError (node:internal/errors:399:5)
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:79:11)
    at defaultGetFormat (node:internal/modules/esm/get_format:121:38)
    at defaultLoad (node:internal/modules/esm/load:81:20)
    at nextLoad (node:internal/modules/esm/loader:163:28)
    at ESMLoader.load (node:internal/modules/esm/loader:605:26)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:457:22)
    at new ModuleJob (node:internal/modules/esm/module_job:64:26)
    at #createModuleJob (node:internal/modules/esm/loader:480:17)

    
Unknown file extension ".ts" for ...\node_modules\.pnpm\[email protected]_@[email protected]_@[email protected][email protected]_solid-start-node_5s2kio276uhd5touku4ijt66hm\node_modules\solid-start\server\server.ts

TypeError: Unknown file extension ".ts" for ...\node_modules\.pnpm\[email protected]_@[email protected]_@[email protected][email protected]_solid-start-node_5s2kio276uhd5touku4ijt66hm\node_modules\solid-start\server\server.ts
    at new NodeError (node:internal/errors:399:5)
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:79:11)
    at defaultGetFormat (node:internal/modules/esm/get_format:121:38)
    at defaultLoad (node:internal/modules/esm/load:81:20)
    at nextLoad (node:internal/modules/esm/loader:163:28)
    at ESMLoader.load (node:internal/modules/esm/loader:605:26)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:457:22)
    at new ModuleJob (node:internal/modules/esm/module_job:64:26)
    at #createModuleJob (node:internal/modules/esm/loader:480:17)

Interestingly, as soon as I disable in my vite.config.ts

import solid from "solid-start/vite";
import { defineConfig } from "vite";
import vercel from "solid-start-vercel";
export default defineConfig(() => {
    return {
        plugins: [solid({ ssr: true, adapter: vercel({ edge: true }) })],
    };
});

import solid from "solid-start/vite";
import { defineConfig } from "vite";
import vercel from "solid-start-vercel";
export default defineConfig(() => {
    return {
        plugins: [solid({ ssr: true, adapter: vercel({ edge: true }) })],
    };
});

everything works. Except ssr of course. Funnily enough, when I try to deploy on vercel without SSR, I get the exact from last year (https://github.com/solidjs/solid-start/issues/383) except that it should have been fixed already. (I'm on 0.2.30)

1 replies

Gaming

Programming