Skip to content

Use compat to get around wasm weirdness #12

Use compat to get around wasm weirdness

Use compat to get around wasm weirdness #12

Triggered via push September 23, 2024 15:25
Status Failure
Total duration 31s
Artifacts

publish.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
deploy: src/game.ts#L14
Cannot find module '@dimforge/rapier2d' or its corresponding type declarations.
deploy: src/mixins/bodyWireframe..ts#L3
Cannot find module '@dimforge/rapier2d' or its corresponding type declarations.
deploy: src/overlay.ts#L3
Cannot find module '@dimforge/rapier2d' or its corresponding type declarations.
deploy: src/terrain/index.ts#L1
Cannot find module '@dimforge/rapier2d' or its corresponding type declarations.
deploy: src/utils/index.ts#L1
Cannot find module '@dimforge/rapier2d' or its corresponding type declarations.
deploy: src/weapons/grenade.ts#L7
Cannot find module '@dimforge/rapier2d' or its corresponding type declarations.
deploy: src/world.ts#L4
Cannot find module '@dimforge/rapier2d' or its corresponding type declarations.
deploy: src/world.ts#L46
Parameter 'collider1' implicitly has an 'any' type.
deploy: src/world.ts#L46
Parameter 'collider2' implicitly has an 'any' type.
deploy: src/world.ts#L46
Parameter 'started' implicitly has an 'any' type.
deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/