valknar/vpinball-wasm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
30 Commits 1 Branch 7 Tags
bf818bdd29ce0e6e4a4459ec32e1d5771e77eaaf
Commit Graph
8 Commits
Author SHA1 Message Date
valknarandClaude Sonnet 5 0f945ed68e Bump version to 0.3.3 for the dispose() hang fix
CI / Build wasm engine (push) Successful in 11m16s
Details 
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
 2026-08-24 10:12:51 +02:00
valknarandClaude Sonnet 5 6ff116ba02 Bump version to 0.3.2 for the MsgBox fix
CI / Build wasm engine (push) Successful in 10m55s
Details 
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
 2026-08-23 19:31:05 +02:00
valknarandClaude Sonnet 5 c7f7cb6afa Bump version to 0.3.1 for the focus-loss freeze fix
CI / Build wasm engine (push) Successful in 10m50s
Details 
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
 2026-08-23 15:17:21 +02:00
valknarandClaude Sonnet 5 6c8d08e618 Bump version to 0.3.0 for the PinMAME integration release
CI / Build wasm engine (push) Failing after 2m19s
Details 
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SoSarxLgY33Kax5UNXcafZ
 2026-08-23 12:38:16 +02:00
valknarandClaude Sonnet 5 d91ef0c96d Rename package to scoped @valknar/vpinball-wasm
CI / Build wasm engine (push) Successful in 9m24s
Details 
Reverts the earlier unscoping: an unscoped package on a Gitea npm
registry has no `.npmrc` mapping a consumer can use other than pinning
the exact tarball URL, since Gitea's registry doesn't proxy npmjs.org
and only scoped packages support the standard `@scope:registry=`
config. Scoping restores that: consumers add one `@valknar:registry=`
line and depend on a normal semver range.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012hQoM3jJT1Lx7CMTciMzvD
 2026-08-23 01:06:15 +02:00
valknarandClaude Sonnet 5 ad66bbf6be Rename package from @valknar/vpinball-wasm to vpinball-wasm
CI / Build wasm engine (push) Successful in 9m32s
Details 
Unscoped, matching this project's other Gitea-published package
(triggershell) - the registry is already scoped to the right owner via
publishConfig.registry's URL path (.../valknar/npm/), so an npm scope
on the package name itself is redundant. The old @valknar/vpinball-wasm
package published under the previous name is being removed manually.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
 2026-08-22 19:06:44 +02:00
valknarandClaude Sonnet 5 536e09dff4 Bump version to 0.1.0 for the first release
CI / Build wasm engine (push) Successful in 9m17s
Details
CI / Publish to npm registry (push) Canceled after 3m47s
Details 
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
 2026-08-22 18:36:26 +02:00
valknar 0a63835689 Scaffold vpinball-wasm: Emscripten port of Visual Pinball
CI / Build wasm engine (push) Failing after 3m30s
Details
CI / Publish to npm registry (push) Skipped
Details 
Build scripts, CMake/source patches, npm packaging, and a Gitea CI
workflow to compile the real Visual Pinball engine (SDL3 + WebGL2 +
libwinevbs for real VBScript) to WebAssembly.

The patches are validated end-to-end: the patched engine boots in a
real browser, loads a real .vpx table, compiles its real GLSL shaders,
computes environment map radiance, initializes physics, and starts the
VBScript engine, before hanging on the one deliberately-deferred piece
of work (game loop rewrite around emscripten_set_main_loop), documented
in the README's roadmap.
 2026-08-22 14:30:14 +02:00