calathus
calathus
PostsComments
SSolidJS
Created by Ho-kage on 10/18/2024 in #support
SolidStart 1.0 and Deno 2.0
-A may work because there are more parameters to allow something?? but I did not such error message.
17 replies
SSolidJS
Created by Ho-kage on 10/18/2024 in #support
SolidStart 1.0 and Deno 2.0
I was able to run with the -A option after removing css, server, build, and optimizeDeps. However, I'm still encountering an error when parsing vite.config.mjs with explicit parameters: javascript TypeError: Cannot read properties of null (reading 'on') It seems this error occurs because stdio is null. It’s strange that a subset of the -A option causes an error, while -A itself works fine. In any case, if the existing configuration doesn’t work, the migration might not be straightforward. You may be able to reproduce this issue with the following vite.config.mjs: 
import { defineConfig } from 'npm:[email protected]';
import deno from '@deno/vite-plugin';
import solidPlugin from 'npm:[email protected]';

export default defineConfig({
  plugins: [deno(), solidPlugin()],
  resolve: {
    alias: {
      '@': '/src',
    },
  },
  css: {
    preprocessorOptions: {
      css: {
        additionalData: '@import "@/styles/global.css";',
      },
    },
  },
  server: {
    port: 3000,
  },
  build: {
    target: 'esnext',
  },
  optimizeDeps: {
    // This might help with the esbuild error
    esbuildOptions: {
      target: 'esnext',
    },
  },
});
import { defineConfig } from 'npm:[email protected]';
import deno from '@deno/vite-plugin';
import solidPlugin from 'npm:[email protected]';

export default defineConfig({
  plugins: [deno(), solidPlugin()],
  resolve: {
    alias: {
      '@': '/src',
    },
  },
  css: {
    preprocessorOptions: {
      css: {
        additionalData: '@import "@/styles/global.css";',
      },
    },
  },
  server: {
    port: 3000,
  },
  build: {
    target: 'esnext',
  },
  optimizeDeps: {
    // This might help with the esbuild error
    esbuildOptions: {
      target: 'esnext',
    },
  },
});
Additionally, I often encounter a "too many files open" error.
17 replies
SSolidJS
Created by Ho-kage on 10/18/2024 in #support
SolidStart 1.0 and Deno 2.0
my impression is better to wait until deno2 announce the support of solidjs..
17 replies
SSolidJS
Created by Ho-kage on 10/18/2024 in #support
SolidStart 1.0 and Deno 2.0
this sample worked. but my original case still not work. I needed to put a lot of --alow**, then it ended with error for loading vite.config.mjs by tring to access stdio.on where stdio is null. I put following parameters: deno run --allow-net --allow-read --allow-env --allow-sys --allow-ffi --node-modules-dir --allow-write npm:vite
17 replies
SSolidJS
Created by Ho-kage on 10/18/2024 in #support
SolidStart 1.0 and Deno 2.0
I was bit confused. I was looking at ssr. . I will try that.
17 replies
SSolidJS
Created by Ho-kage on 10/18/2024 in #support
SolidStart 1.0 and Deno 2.0
solid template does not have deno.json. have you test them? it may run, but it won't use deno2.
17 replies
SSolidJS
Created by Ho-kage on 10/18/2024 in #support
SolidStart 1.0 and Deno 2.0
the project contains solid templ;ate, but it does not use deno in package.json, while react version use deno. So solidjs seems not supported yet. I checked teh status using peplexity, I found the above bug report. Anywa, deno 2 solid js are both new, these reports are older then those new release.
17 replies
SSolidJS
Created by Ho-kage on 10/18/2024 in #support
SolidStart 1.0 and Deno 2.0
I tried to run solidjs project using deno2, but vite throws error. Deno2 site also does not mention the support of solidjs. If we can use deno2 with solidjs, it will be perfect combination for web development. I would like to know what is planned for the support of deno2
17 replies