Upstream issues tracking

[lowlighter]

Warning

This is an umbrella issue that covers bug encountered during development but are due to upstream bugs.
Usually a workaround is found in the meantime (if possible) so this is more for maintainers' reference

Scope

repo

Deno

• npx tsx cannot be run through deno task
  • deno task: cannot run tsx denoland/deno#27166
  • "magic behavior" for deno task not mentioned in the doc denoland/docs#1270
  • workaround: use npm test instead
• deno.jsonc cannot use workspaces: [ "@mizu/*" ] because it breaks bundling resolution
  • Resolve error for globstar workspaces lucacasonato/esbuild_deno_loader#156
  • workaround: manually list workspace members
• deno.jsonc have some sleep 0 tasks as placeholder (empty command not supported)
  • deno task: support empty command if dependencies are specified denoland/deno#27165
  • workaround: keep sleep 0 as placeholder
• denoland/deployctl github action does not behaves the same as the cli version
  • deployctl github action is missing a lot of features from the cli version denoland/deployctl#350
  • workaround: parse flags and pass them back as step outputs

  • mizu/.github/workflows/ci.yml

    Lines 61 to 63 in 7a03e8f

    	- name: Run deno task deploy:setup-github-actions
    	run: deno task deploy:setup-github-actions
    	id: setup_github_actions

  • mizu/.github/tools/github_actions_deno_deploy.ts

    Lines 16 to 25 in 7a03e8f

    	// Parse deno.jsonc and print deno deploy flags
    	// deno-lint-ignore no-explicit-any
    	const config = JSONC.parse(await Deno.readTextFile("./deno.jsonc")) as any
    	core.setOutput("project", config.deploy.project)
    	core.setOutput("entrypoint", config.deploy.entrypoint)
    	core.setOutput("include", config.deploy.include.join(","))
    	core.setOutput("exclude", config.deploy.exclude.join(","))
    	core.setOutput("import_map", ".imports_map.json")
    	await Deno.writeTextFile(".imports_map.json", JSON.stringify({ imports: config.imports }, null, 2))

• deployctl conflicts with dependencies installed by npm jsr (e.g. Error: The deployment failed: npm package '@jsr/dprint__formatter' does not exist.)
  • missing dependencies deduplication with jsr when using both package.json and deno.json causes resolution issues denoland/deno#27380
  • feat(action): auto-discovery of deno.json and auto-populate defaults  denoland/deployctl#351
  • workaround: remove lock files and package.json to "reset" the lock file

  • mizu/.github/workflows/ci.yml

    Line 64 in 7a03e8f

    - run: deno install

  • mizu/.github/tools/github_actions_deno_deploy.ts

    Lines 10 to 14 in 7a03e8f

    	// Remove lockfiles and package.json to avoid resolution conflicts
    	// https://github.com/denoland/deno/issues/27380
    	await Deno.remove("deno.lock", { recursive: true })
    	await Deno.remove("package.json", { recursive: true })
    	await Deno.remove("package-lock.json", { recursive: true })

• Bad fmt in mod.html files
  • deno fmt: scripts lost indent in html file denoland/deno#27374
  • No fixes, but not breaking
• Support cleanUrls natively for easy HTTP serving
  • proposal(http): add cleanUrls option to serveDir denoland/std#6232
  • Workaround: use forked version https://jsr.io/@lowlighter/std-http

Deno doc

• The new version of @deno/doc@^0.162.1 is not able to generate documentation for local modules
  • 0.162 throws Error: relative URL without a base, but 0.161 works fine ? denoland/deno_doc#680
  • Workaround: downgrade to version 0.161

Error: relative URL without a base
    at __wbg_new_28c511d9baebfa89 (https://jsr.io/@deno/doc/0.162.1/deno_doc_wasm.generated.js:651:19)
    at <anonymous> (wasm://wasm/011a3ff2:1:136374)
    at <anonymous> (wasm://wasm/011a3ff2:1:3139281)
    at <anonymous> (wasm://wasm/011a3ff2:1:3723228)
    at __wbg_adapter_51 (https://jsr.io/@deno/doc/0.162.1/deno_doc_wasm.generated.js:290:6)
    at real (https://jsr.io/@deno/doc/0.162.1/deno_doc_wasm.generated.js:274:14)
    at ext:core/01_core.js:291:9
    at eventLoopTick (ext:core/01_core.js:175:7)

Node

• npx tsx --test does not find tests on the github runner (but works as expected locally)
  • fixed: was using an outdated version of node

Bun

• bun test currently ignores all tests wrapped by the mod_test.html test runner
  • bun test ignores tests in subsequent files when using a test factory oven-sh/bun#11660
  • NO FIXES, BUN COMPATIBILITY CANNOT BE GUARANTEED ATM
• Cannot pin oven-sh/setup-bun to 1.x
  • Version selectors 1.x/1.0.x result in 400/404 response errors on install oven-sh/setup-bun#37
  • Workaround: use latest instead
• JSDOM doesn't work with bun/windows
  • Possibly related to Support node-canvas oven-sh/bun#5835 ?
  • See Ref [1]
  • NO FIXES, BUN COMPATIBILITY WITH WINDOWS CANNOT BE GUARANTEED ATM

Ref [1]:

# Unhandled error between tests
  -------------------------------
  
  Error: 
        at 2:1
  1 | (function (entry, fetcher)
      ^
  SyntaxError: Export named 'JSDOM' not found in module 'D:\a\mizu\mizu\node_modules\jsdom'.
  -------------------------------