dsherret Comments

i've also been slowly extracting out resolution code from the CLI for use in rolldown and rspack. I have a branch I've been working on to get it working in rolldown, but I'm taking a break for a week because of the Deno 2.2 release next week

23 replies

DDeno

•Created by Bhaumin on 1/29/2025 in #help

Deno Emit for Bundling - Potential Open Source Contributions

i'd recommend using: https://github.com/lucacasonato/esbuild_deno_loader

23 replies

DDeno

•Created by Bhaumin on 12/5/2024 in #help

why deno vs code extension not supporting deno test describe and coverage?

no eta at this point

6 replies

DDeno

•Created by Bhaumin on 12/5/2024 in #help

why deno vs code extension not supporting deno test describe and coverage?

https://github.com/denoland/deno/issues/14804

6 replies

DDeno

•Created by con_ on 10/9/2024 in #help

Guidance in testing new publish flag

you could make a copy of the tests/specs/publish/successful directory and give it a descriptive name, edit the __test__.jsonc file, then run cargo test specs::publish to run the tests

3 replies

DDeno

•Created by Adam Harris on 9/26/2024 in #help

In a deno/npm hybrid monorepo, what are the options for importing a deno member from a npm member?

3 replies

DDeno

•Created by J on 9/24/2024 in #help

deno not recognized

does the file actually exist at that location? and is that location in echo $env:PATH?

4 replies

DDeno

•Created by Sean Knowles on 8/30/2024 in #help

Workspaces issue: Error running deno run dev command while starting Oak server

sorry, I'm just away from my computer getting lunch awesome! I'm glad that worked. Yeah then once workspace support lands in deploy you can remove all that.

48 replies

DDeno

•Created by Sean Knowles on 8/30/2024 in #help

Workspaces issue: Error running deno run dev command while starting Oak server

then once workspace support lands in Deploy you can remove that and actually switch to workspaces

48 replies

DDeno

•Created by Sean Knowles on 8/30/2024 in #help

Workspaces issue: Error running deno run dev command while starting Oak server

just checked in on the status of workspaces and the implementation in deploy is being worked on at the moment. I don't have an estimate for when it will be supported, but you can manually write in the resolution in the meantime in the main deno.json that gets resolved in deploy https://docs.deno.com/runtime/manual/basics/import_maps/ To re-iterate, instead of relying on the automatic workspace resolution, you can manually write it in the import map (deno.json) like this:

{
  "imports": {
    "@scope/server": "../relative-path-to-package/mod.ts"
    "@scope/server/some-export": "../relative-path-to-package/some-export.ts"
  }
}

{
  "imports": {
    "@scope/server": "../relative-path-to-package/mod.ts"
    "@scope/server/some-export": "../relative-path-to-package/some-export.ts"
  }
}

48 replies

DDeno

•Created by Sean Knowles on 8/30/2024 in #help

Workspaces issue: Error running deno run dev command while starting Oak server

based on that error message you posted though, it looks like workspace support hasn't landed in deploy yet. I'll check now for sure though. You can work around it by using an import map and mapping the specifiers like "@scope/server": "../relative-path-to-package/mod.ts"

48 replies

DDeno

•Created by Sean Knowles on 8/30/2024 in #help

Workspaces issue: Error running deno run dev command while starting Oak server

for deno deploy, i'd recommend unsetting the experimental DENO_FUTURE=1 and see if it works then

48 replies