biome: πŸ› Missing field `pullCodeActions` when using `biome.formatContent()` with `@biomejs/js-api@0.8.0-beta.1` & `@biomejs/wasm-nodejs@2.0.0-beta.4`

Environment information

CLI:
  Version:                      2.0.0-beta.4
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         xterm-ghostty
  JS_RUNTIME_VERSION:           v24.0.1
  JS_RUNTIME_NAME:              node
  NODE_PACKAGE_MANAGER:         yarn/4.9.1

Biome Configuration:
  Status:                       Loaded successfully
  Path:                         biome.json
  Formatter enabled:            true
  Linter enabled:               true
  Assist enabled:               true
  VCS enabled:                  true

Workspace:
  Open Documents:               0

What happened?

Error: missing field pullCodeActions when using formatContent

Description

When attempting to format TypeScript code using the @biomejs/js-api package, an internal WASM error occurs with the message Error: missing field 'pullCodeActions'. The error happens specifically when calling the biome.formatContent() method.

Error message

Error: Error: missing field pullCodeActions
at module.exports.wbg_new_c68d7209be747379 (biome_wasm.js:703:17)
at null.<anonymous> (wasm://wasm/047f06ce:1:15474924)
at null.<anonymous> (wasm://wasm/047f06ce:1:14267400)
at null.<anonymous> (wasm://wasm/047f06ce:1:15297502)
at Workspace.pullDiagnostics (biome_wasm.js:489:26)
...
at Biome.formatContent (index.ts:208:15)

Expected result

The code formatter should successfully format the TypeScript content without throwing the WASM error about missing fields.

Code of Conduct

  • I agree to follow Biome’s Code of Conduct

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (7 by maintainers)

Most upvoted comments

Thank you for the quick response! Will investigate it.