Process completed with exit code 1.

Need to wrap this literal in a JSX expression

Missing JSX expression container around literal string: "Nested content"

Need to wrap this literal in a JSX expression

Missing JSX expression container around literal string: "Hello World"

All imports in the declaration are only used as types. Use `import type`

Missing trailing comma

Missing trailing comma

Missing trailing comma

A space is required before '}'

The strategy configuration was canceled because "build._24" failed

The operation was canceled.

Need to wrap this literal in a JSX expression

Missing JSX expression container around literal string: "Nested content"

Need to wrap this literal in a JSX expression

Missing JSX expression container around literal string: "Hello World"

All imports in the declaration are only used as types. Use `import type`

Missing trailing comma

Missing trailing comma

Missing trailing comma

A space is required before '}'

The strategy configuration was canceled because "build._24" failed

The operation was canceled.

The strategy configuration was canceled because "build._24" failed

The operation was canceled.

Need to wrap this literal in a JSX expression

Missing JSX expression container around literal string: "Nested content"

Need to wrap this literal in a JSX expression

Missing JSX expression container around literal string: "Hello World"

All imports in the declaration are only used as types. Use `import type`

Missing trailing comma

Missing trailing comma

Missing trailing comma

A space is required before '}'

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. 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/

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. 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/

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. 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/