DSH Community Market npm test plugin

This is a minimal, harmless Host plugin used to test npm discovery and managed installation in DSH Community Market. Version 1.0.3 opts its bundled community-market-smoke-test skill into Community Market hot loading.

Publish

The scoped package name @heyvin/dsh-community-market-test was confirmed as unavailable on the public npm registry on 2026-08-30. Log in to public npm, then publish from this directory:

npm login --registry=https://registry.npmjs.org/
npm test
npm publish --access public

publishConfig fixes the destination to the public npm registry even when the machine's default npm registry points somewhere else.

Find it in Community Market

The package contains the exact keyword webank-dsh-plugin. For this public npm test, first point the machine's default npm registry at https://registry.npmjs.org/. In DSH Desktop, add and select the WeBank WNPM source, then set Sources → npm plugin recognition rules to:

Package name prefixes: @heyvin/dsh-
npm keywords: webank-dsh-plugin

Market first checks @heyvin:registry and falls back to the default registry when that scoped setting is absent. Refresh the catalog and search for:

@heyvin/dsh-community-market-test

Install it from the plugin details dialog and restart DSH Desktop. A successful load writes this harmless Host log message:

@heyvin/dsh-community-market-test: plugin loaded successfully

Test the bundled skill

After installing version 1.0.1 and restarting DSH Desktop, version 1.0.2 verified the first hot update. Publish version 1.0.3 while DSH Desktop remains open, refresh the Installed view, and click Update skills. Then enter the same invocation again:

/community-market-smoke-test

The model must reply with exactly:

1.0.3

Do not restart between updating the skills to 1.0.3 and invoking the skill. The version response verifies that Community Market loaded the declared dsh.communityMarket.hotSkills file from the updated npm package without reloading package code or the active profile.

To test update detection later, publish another stable version. npm versions are immutable, so always bump the version instead of attempting to republish an existing version.