Skip to content

Publish npm package #17

Publish npm package

Publish npm package #17

Triggered via release June 6, 2026 16:41
Status Failure
Total duration 34s
Artifacts –

npm-publish.yml

on: release
Publish to npm
31s
Publish to npm
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
Publish to npm: src/dashboard/marked.min.js#L6
Unnecessary escape character: \[
Publish to npm: src/dashboard/marked.min.js#L6
'e' is defined but never used
Publish to npm: src/dashboard/marked.min.js#L6
Unnecessary escape character: \[
Publish to npm: src/dashboard/marked.min.js#L6
'self' is not defined
Publish to npm: src/dashboard/marked.min.js#L6
The value assigned to 'e' is not used in subsequent statements
Publish to npm: src/dashboard/marked.min.js#L6
'define' is not defined
Publish to npm: src/dashboard/marked.min.js#L6
'define' is not defined
Publish to npm: src/dashboard/marked.min.js#L6
'exports' is not defined
Publish to npm: src/dashboard/marked.min.js#L6
Expected an assignment or function call and instead saw an expression
Publish to npm: src/dashboard/marked.min.js#L6
Expected an assignment or function call and instead saw an expression
Publish to npm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Publish to npm: src/tui/execute-plan-panel.tsx#L65
The reactive variable 'props.planContent' should be used within JSX, a tracked scope (like createEffect), or inside an event handler function, or else changes will be ignored