Thomas Comments

Thomas

•Created by ginpacc on 8/2/2024 in #help

node:worker_threads "Module not found"

Hi, demo compile cannot know what kind of worker file is loaded. You can use --include to specify which file should be included.

4 replies

DDeno

•Created by Thomas on 7/20/2024 in #help

Demo for Desktop App

That was just a typo on my part. I meant --no-terminal, of course. --no-terminal does not work as expected and there is already an issue.

10 replies

DDeno

•Created by Thomas on 7/9/2024 in #help

Is dynamic import a slow type?

@Mark G Thanks, and now I have also found the slow-type in my code. There was a type that derived from an interface. Something like:

export interface ISomething {
 //...
}
export type TSomething = ISomething;

export interface ISomething {
 //...
}
export type TSomething = ISomething;

8 replies

DDeno

•Created by Thomas on 7/9/2024 in #help

Is dynamic import a slow type?

I guess I'm blind 😅 I would really like to understand it. I don't see where slow-types should be in the code of my package.

8 replies

DDeno

•Created by Thomas on 7/9/2024 in #help

Is dynamic import a slow type?

@Deno AI Helper Should the command "deno lint" reveal all slow-types?

8 replies

DDeno

•Created by kimbleton on 6/17/2024 in #help

Using bitbucket repositories as dependencies in Deno

Long time ago, I tried the same with gitlab. Someone else already tried it with Azure DevOps. None of that works. I think there is already an issue about it.

14 replies

DDeno

•Created by Thomas on 5/7/2024 in #help

reflect-metadata on Deno Deploy not working?

And @deno/emit does not seem to be an alternative to bundling either, because here I get the following error message:

error: Uncaught (in promise) Error: Unable to output during bundling: load_transformed failed: failed to analyze module: failed to resolve /v135/.@latest/denonext/deno.json.js from https://esm.sh/v135/@jsr/std__http@0.221.0/denonext/file-server.js: Cannot resolve "/v135/.@latest/denonext/deno.json.js" from "https://esm.sh/v135/@jsr/std__http@0.221.0/denonext/file-server.js".
      const ret = new Error(getStringFromWasm0(arg0, arg1));
                  ^
    at __wbg_new_28c511d9baebfa89 (https://jsr.io/@deno/emit/0.40.2/emit.generated.js:556:19)
    at <anonymous> (file:///home/runner/.local/share/deno-wasmbuild/96bf0f6a753e71948f71b7a491baca4d34264a2622a74d137b5ff37e4d86f571.wasm:1:3526399)
    at <anonymous> (file:///home/runner/.local/share/deno-wasmbuild/96bf0f6a753e71948f71b7a491baca4d34264a2622a74d137b5ff37e4d86f571.wasm:1:485448)
    at <anonymous> (file:///home/runner/.local/share/deno-wasmbuild/96bf0f6a753e71948f71b7a491baca4d34264a2622a74d137b5ff37e4d86f571.wasm:1:2094778)
    at <anonymous> (file:///home/runner/.local/share/deno-wasmbuild/96bf0f6a753e71948f71b7a491baca4d34264a2622a74d137b5ff37e4d86f571.wasm:1:3244744)
    at __wbg_adapter_46 (https://jsr.io/@deno/emit/0.40.2/emit.generated.js:246:8)
    at real (https://jsr.io/@deno/emit/0.40.2/emit.generated.js:231:14)
    at ext:core/01_core.js:302:9
    at eventLoopTick (ext:core/01_core.js:168:7)
Error: Process completed with exit code 1.

error: Uncaught (in promise) Error: Unable to output during bundling: load_transformed failed: failed to analyze module: failed to resolve /v135/.@latest/denonext/deno.json.js from https://esm.sh/v135/@jsr/std__http@0.221.0/denonext/file-server.js: Cannot resolve "/v135/.@latest/denonext/deno.json.js" from "https://esm.sh/v135/@jsr/std__http@0.221.0/denonext/file-server.js".
      const ret = new Error(getStringFromWasm0(arg0, arg1));
                  ^
    at __wbg_new_28c511d9baebfa89 (https://jsr.io/@deno/emit/0.40.2/emit.generated.js:556:19)
    at <anonymous> (file:///home/runner/.local/share/deno-wasmbuild/96bf0f6a753e71948f71b7a491baca4d34264a2622a74d137b5ff37e4d86f571.wasm:1:3526399)
    at <anonymous> (file:///home/runner/.local/share/deno-wasmbuild/96bf0f6a753e71948f71b7a491baca4d34264a2622a74d137b5ff37e4d86f571.wasm:1:485448)
    at <anonymous> (file:///home/runner/.local/share/deno-wasmbuild/96bf0f6a753e71948f71b7a491baca4d34264a2622a74d137b5ff37e4d86f571.wasm:1:2094778)
    at <anonymous> (file:///home/runner/.local/share/deno-wasmbuild/96bf0f6a753e71948f71b7a491baca4d34264a2622a74d137b5ff37e4d86f571.wasm:1:3244744)
    at __wbg_adapter_46 (https://jsr.io/@deno/emit/0.40.2/emit.generated.js:246:8)
    at real (https://jsr.io/@deno/emit/0.40.2/emit.generated.js:231:14)
    at ext:core/01_core.js:302:9
    at eventLoopTick (ext:core/01_core.js:168:7)
Error: Process completed with exit code 1.

6 replies

DDeno

•Created by Thomas on 5/7/2024 in #help

reflect-metadata on Deno Deploy not working?

Looks like bundeling is not an option either, because I use @oak/oak and oak uses the node specifier. And deno bundle does not support node specifier.

6 replies

DDeno

•Created by Thomas on 5/7/2024 in #help

reflect-metadata on Deno Deploy not working?

That is not very helpful. Especially not point 6, because my goal is to be able to use a dependency injection like in Angular, Nestjs, tsyringe or Danet on Deno Deploy. The problem seems to be the compiler option emitDecoratorMetadata which is probably not supported on Deno Deploy (see https://github.com/denoland/deploy_feedback/issues/633). Danet probably had the same problem and solved it by bundling the application. But deno bundle is deprecated so I would have to use a third party bundler, which is not great either.

6 replies

DDeno

•Created by Thomas on 3/27/2024 in #help

How to install jupyter using deno v1.41.x

My mistake. The "--unstable" flag is not necessary. If you execute the command without "--unstable", you get the following warning:

Warning "deno jupyter" is unstable and might change in the future.

Warning "deno jupyter" is unstable and might change in the future.

If you execute the command with "--unstable", you will receive the following warning:

⚠️ The `--unstable` flag is deprecated and will be removed in Deno 2.0. Use granular `--unstable-*` flags instead.
Learn more at: https://docs.deno.com/runtime/manual/tools/unstable_flags
Warning "deno jupyter" is unstable and might change in the future.

⚠️ The `--unstable` flag is deprecated and will be removed in Deno 2.0. Use granular `--unstable-*` flags instead.
Learn more at: https://docs.deno.com/runtime/manual/tools/unstable_flags
Warning "deno jupyter" is unstable and might change in the future.

But my mistake was that I forgot to install JupyterLab. In the end everything seems to be correct.

4 replies

DDeno

•Created by GuillaumeRobinInarix on 3/22/2024 in #help

Import package from Azure DevOps repository

Okay, I was curious and tried it with Gitlab (don't have access to an Azure DevOps) and also failed.

11 replies

DDeno

•Created by GuillaumeRobinInarix on 3/22/2024 in #help

Import package from Azure DevOps repository

Why? It should work. See the documentation: https://docs.deno.com/runtime/manual/basics/modules/private

11 replies

DDeno

•Created by Mqx on 3/11/2024 in #help

Import SCSS in TS files

I'm not sure, but Deno itself can't do anything with CSS or SCSS. Support for these files therefore seems rather inconsistent. And, on the other hand, do we still need SCSS today (in the age of CSS3)? And yes, ts-ignore is not a good solution, of course. Maybe you can go a different way instead. Here is an example of how you could use CSS programmatically (probably for jsx?): https://docs.deno.com/runtime/manual/advanced/jsx_dom/css Not sure if this is helpful 😅

51 replies

DDeno

•Created by Chicoo+52 on 3/13/2024 in #help

How installing Silverbullet on deno

I found instructions for using it on Deno-Deploy on their github repo: https://github.com/silverbulletmd/silverbullet/blob/main/website/Install/Deno%20Deploy.md

3 replies

DDeno

•Created by Mqx on 3/11/2024 in #help

Import SCSS in TS files

If it works, you can simply set an ts-ignore.

// @ts-ignore
import style from "style.scss"

// @ts-ignore
import style from "style.scss"

51 replies

DDeno

•Created by Mqx on 3/11/2024 in #help

Import SCSS in TS files

I'm not that familiar with lit and esbuild. But you are trying to compile a frontend with esbuild using Deno. And this seems to be successful (great :deno_thumbs_up:). The Deno linter is not designed for frontend. Bug maybe you can exclude the frontend code for the deno-linter (deno.json) ....

{
  ...
  "lint": {
    "exclude": [
      "ui/"
    ]
  }
}

{
  ...
  "lint": {
    "exclude": [
      "ui/"
    ]
  }
}

...and configure eslint for your frontend instead?

51 replies

DDeno

•Created by Thomas on 3/9/2024 in #help

Best practice for releasing a deno package on GitHub

@NeTT Interesting reaction. May I ask for your opinion on this? 😀

6 replies

DDeno

•Created by Thomas on 3/9/2024 in #help

Best practice for releasing a deno package on GitHub

I know how to publish. I am interested in automating the release process (which can be done with sematic-release in node). - Increase version in deno.json (depending on commit messages) - Create tag - Create release

6 replies

DDeno

•Created by Thomas on 3/5/2024 in #help

Should deno install work with jsr?

It looks like a bug to me. I have created an issue: https://github.com/denoland/deno/issues/22754

5 replies

DDeno

•Created by Thomas on 3/5/2024 in #help

Should deno install work with jsr?

@marvinh. I updated my post.

5 replies