publish error different on CI
I run this command:
on my local project and in the CI....
pnpm exec deno publish --dry-run --unstable-sloppy-imports --allow-dirty
pnpm exec deno publish --dry-run --unstable-sloppy-imports --allow-dirty
Ambiguous linting on import type and jsdoc
I want to enforce the usage of
import type when no value is referenced in the module, and it works most of the time.
The issue happens when I reference another type using @see in jsdoc, this is very common for foreign keys in DAO / Entity interfaces such as Drizzle / Kysely.
When this kind of reference exists, import type results in errors inside the jsdoc for value referencing; while normal imports results in the lint error of verbatim-module-syntax itself....Custom Lint rule not applying in IDE with Deno Extension
When I'm using a custom lint rule, it applies the rule correctly when using
deno lint but it is not applying the rule in the regular VS Code IDE. Is that expected behavior, or am I potentially missing an implementation piece that does that dynamic analysis.Load Typescript into deno_core::extension!
Hello,
As we know, deno_core provide extension that makes possible to create "built-in" functions or classes. But, I want to provide a typed API, if possible via Typescript.
Currently, I use deno_core to implement function to extract / mining data in Typescript. It will be very convenient to also provide built-in types that has type....
square
looks like the Square API is not compatable with Square "npm:square", what are people using to interface with Square APIs?
[Bug]: Deno expects text or bytes files lines to be in Quotation marks
I've two files that I wanted to import, trying to import them either as text or bytes results in Deno trying to parse them as javascript unless the lines were inside double quotations
```ts
import wgServerPublicKey from "@wg-server-publickey" with { type: "bytes", encoding: "utf-8" }; // same error if type: text
import wgServerConfig from "@wg-server-config" with { type: "bytes" }; // same error if type: text...
Failing to create import alias for tauri project
Hello everyone. I created a tauri project recently with deno and one of the things I'm trying to setup are aliases so I don't have to use relative imports within my vue files.
As per docs, I created a deno.json file in the project's root:
```
{
"$schema": "https://raw.githubusercontent.com/denoland/deno/refs/heads/main/cli/schemas/config-file.v1.json",...
getting a "TypeError: t.expireTags is not a function" on deploy-ea with Next.js
When calling a server function that includes
revalidatePath i get a "TypeError: t.expireTags is not a function" error.
Did anyone encounter a similar problem?
Building and running this locally does not produce the error....Node compat for `matchesGlob` from `node:path`?
Hi there 👋
I'm new here but have been a deno fan from the get-go and have several project running on deno deploy v1 and v2 - love it!
I'm using deno 2.5.2 locally...
CSP related complications
Content Security Policy of your site blocks the use of 'eval' in JavaScript I am getting this in the browser. I am trying to access ws://localhost:5712/ws from an island.Auto type generation with ReactRouter + Vite + Deno
I'm attempting to get ReactRouter working with Vite + Deno. My application runs fine, but I'm running into static type issues in the IDE. (first image)
My main files are
.tsx files, but for some reason the type generation is generating the path via .js instead. (second image).
...
Is it possible to run --unstable-raw-imports flag in Deno Deploy (classic)?
Getting a
The deployment failed: The import attribute type of "text" is unsupported when trying to deploy on Deno Deploy Classic with text based import attributes: import example from "./some/file.txt" with { type: "text" }
Works fine locally when adding "unstable": ["raw-imports"], in deno.jsonc or even running with the --unstable-raw-imports flag as per Deno docs. Maybe this is not (yet?) supported on Deno Deploy?...How to prevent Deno from automatic dependencies installation during `deno task`? Why does it happen?
Hey! I have a few problems with deps and
deno task.
One is, I have my own install task that is running deno install with certain arguments (e.g. --allow-scripts, --env-file etc). However, if I run deno task install, it first installs the dependencies, before running my task. This is confusing and I don't know how to disable it.
Another is, Deno unexpectedly updates the lockfile when I don't ask it to. Here is a failing workflow: link. After installing packages with deno install (with frozen lockfile) in the workspace root, everything is fine. However, when running a task from a workspace member at tests/node (the command is vitest run), Deno errors me that the lockfile is out of date - for some reason, it wants to add another entry for npm:vitest....Doppler Integration Broken w/ DD EA
Deno Deploy's Doppler integration doesn't work with new PATs generated in Account Settings in EA, but when I go to use an org in classic that API key is recognized. Just curious if I'm doing something wrong or need to do something different. Thank you!
Deno compile with --include
Hi, playing around with
deno compile --include following the docs probably doing something wrong but not sure what. Help appreciated, using v2.5.3. I have the following
names.tsv
```tsv
John Doe...Playwright error requires Node.js v18.19 or higher
I'm attempting to run Playwright, within the context of Deno, but for some reason I receive this playwright error that Node.JS is required to load ESM modules. I am using Deno 2.5.3, and running playwright.config.mts file from the root level with
deno run playwright test I do have Node 20, 22, and 24 installed, and I tested with Node 20 and 24 and received the same error.Has the v8.getHeapSnapshot function been implemented?
When I try to use this function, I get the following error:
```
error: Error: Not implemented: v8.getHeapSnapshot
at notImplemented (ext:deno_node/_utils.ts:9:9)...
Help use enviroment variable for both Deno and SvelteKit
Changed post since I solved the original issue.
Now I'm having a very annoying issue with trying to use an enviroment variable that works for both Deno and SveltKit....
Problem with Deno's compile
I have updated to deno 2.5.3 yesterday (stable release, aarch64-apple-darwin) and, since then, I have problems with deno compile even when I use it on a one-liner typescript file (i.e., console.log('Hello world').
At first, I got a load of warnings about symbolic links that were wrong (no target). I took care of those but, nevertheless, the deno process did not finish even after several minutes; I had to kill it manually.
What was strange is that the symbolic links referred to files and directories that had absolutely nothing to do with the oneliner ts file, or even with deno in general. (Old projects still around on my disc, whether in typescript or not.) I attempted to run it in the background and what I seemed to understand is that the process was doing file i/o all over the place. As if it was scanning my disk....