Skip to content

Conversation

@eymar
Copy link

@eymar eymar commented Nov 7, 2025

wasm -> wasmJs

When following README.md it's convenient when the snippets are up-to-date.


Btw, it might be even more convenient if the plugin would show a warning or even an error when a registered target doesn't exist.

When following a README.md it's convenient when the snippets are up-to-date
@eymar eymar changed the title Use correct name for wasmJs target in README.md Correct the name of k/wasm target in README.md Nov 7, 2025
@fzhinkin
Copy link
Collaborator

fzhinkin commented Nov 7, 2025

@eymar, thanks for opening the PR.

The plugin already shows a warning when a non-existing target is registered, for example:

Cannot find a benchmark compilation 'wasm', ignoring.

Note that the README is correct:

  • in the first step (a few lines above of your change), the wasm target is configured
  • given that it is still possible (removal is scheduled to 2.3) to specify wasm target (without Js suffix), everything works fine (modulo a warning about wasm deprecation)

But yeah, the README should use up-to-date target names.

Could you please also update this line to use wasmJs instead of wasm?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants