shultz🇮🇱 Comments

shultz🇮🇱

Posts Comments

DDeno

•Created by Necmttn | Craftgen.ai on 5/30/2024 in #help

Writing modules for multiple runtime ( Deno & browser ) + Monorepo setup?

if you need a monorepo maybe do something temporary until deno 2 which shouldn't be that far off

8 replies

DDeno

•Created by shultz🇮🇱 on 5/29/2024 in #help

Loading failed for the module with source “node:process” - island not hydrating

yes it seems to be related to the error Loading failed for the module with source “node:process”.

5 replies

DDeno

•Created by shultz🇮🇱 on 5/29/2024 in #help

Loading failed for the module with source “node:process” - island not hydrating

The component needs document so it can only render on client

5 replies

DDeno

•Created by shultz🇮🇱 on 5/29/2024 in #help

Loading failed for the module with source “node:process” - island not hydrating

Error in console is: Loading failed for the module with source “node:process”.

5 replies

DDeno

•Created by shultz🇮🇱 on 5/29/2024 in #help

preact/compat

this looks ok:

  "compilerOptions": {
    "jsx": "react-jsx",
    "jsxImportSource": "preact",
}
  "imports": {
    "$fresh/": "https://deno.land/x/fresh@1.6.8/",
    "preact": "https://esm.sh/preact@10.19.6",
    "preact/": "https://esm.sh/preact@10.19.6/",
    "react": "https://esm.sh/v135/preact@10.19.6/compat",
    "react-dom": "https://esm.sh/v135/preact@10.19.6/compat",
    "react/jsx-runtime": "npm:preact/jsx-runtime",
    "@types/react": "https://esm.sh/preact@10.19.3/compat"
}

  "compilerOptions": {
    "jsx": "react-jsx",
    "jsxImportSource": "preact",
}
  "imports": {
    "$fresh/": "https://deno.land/x/fresh@1.6.8/",
    "preact": "https://esm.sh/preact@10.19.6",
    "preact/": "https://esm.sh/preact@10.19.6/",
    "react": "https://esm.sh/v135/preact@10.19.6/compat",
    "react-dom": "https://esm.sh/v135/preact@10.19.6/compat",
    "react/jsx-runtime": "npm:preact/jsx-runtime",
    "@types/react": "https://esm.sh/preact@10.19.3/compat"
}

6 replies

DDeno

•Created by shultz🇮🇱 on 5/7/2024 in #help

npm specifier not found in LSP only, and so no types for certain imports

filed a bug here: https://github.com/denoland/deno/issues/23734

11 replies

DDeno

•Created by shultz🇮🇱 on 5/7/2024 in #help

npm specifier not found in LSP only, and so no types for certain imports

btw this still appears in the lsp output view

Could not set npm package requirements. Error getting response at https://registry.npmjs.org/@types/node for package "@types/node": An npm specifier not found in cache: "@types/node", --cached-only is specified.

Could not set npm package requirements. Error getting response at https://registry.npmjs.org/@types/node for package "@types/node": An npm specifier not found in cache: "@types/node", --cached-only is specified.

11 replies

DDeno

•Created by shultz🇮🇱 on 5/7/2024 in #help

npm specifier not found in LSP only, and so no types for certain imports

yes, thanks! I didn't have a lock file, but had "lock:false" in deno.json. changing to lock:true fixes the issue. deleting the lock file and changing back to lock:false and the problem returns. it does seem like a bug

11 replies

DDeno

•Created by shultz🇮🇱 on 5/7/2024 in #help

npm specifier not found in LSP only, and so no types for certain imports

is there any reccomendation about how to debug it further?

11 replies

DDeno

•Created by shultz🇮🇱 on 5/7/2024 in #help

npm specifier not found in LSP only, and so no types for certain imports

It seems the LSP is unable to resolve something that needs "@types/node" and than bails out. for some reason deno cache has no problem

11 replies

DDeno