Untitled

mail@pastecode.io avatar
unknown
plain_text
a year ago
5.0 kB
2
Indexable
Never
āžœ  frontend git:(playwright-setup) āœ— yarn install
yarn install v1.22.19
[1/5] šŸ”  Validating package.json...
[2/5] šŸ”  Resolving packages...
success Already up-to-date.
$ husky install
husky - Git hooks installed
āœØ  Done in 0.58s.
āžœ  frontend git:(playwright-setup) āœ— yarn test-docker
yarn run v1.22.19
$ docker run --rm --network host -v $(pwd):/work/ -w /work/ -it mcr.microsoft.com/playwright:v1.26.0-focal yarn test-ct
yarn run v1.22.19
$ playwright test -c playwright-ct.config.ts

Running 6 tests using 2 workers

vite v3.1.4 building for production...
āœ“ 2 modules transformed.
[vite:esbuild] 
You installed esbuild for another platform than the one you're currently using.
This won't work because esbuild is written with native code and needs to
install a platform-specific binary executable.

Specifically the "esbuild-darwin-arm64" package is present but this platform
needs the "esbuild-linux-arm64" package instead. People often get into this
situation by installing esbuild on Windows or macOS and copying "node_modules"
into a Docker image that runs Linux, or by copying "node_modules" between
Windows and WSL environments.

If you are installing with npm, you can try not copying the "node_modules"
directory when you copy the files over, and running "npm ci" or "npm install"
on the destination platform after the copy. Or you could consider using yarn
instead of npm which has built-in support for installing a package on multiple
platforms simultaneously.

If you are installing with yarn, you can try listing both this platform and the
other platform in your ".yarnrc.yml" file using the "supportedArchitectures"
feature: https://yarnpkg.com/configuration/yarnrc/#supportedArchitectures
Keep in mind that this means multiple copies of esbuild will be present.

Another alternative is to use the "esbuild-wasm" package instead, which works
the same way on all platforms. But it comes with a heavy performance cost and
can sometimes be 10x slower than the "esbuild" package, so you may also not
want to do that.

Error: 
You installed esbuild for another platform than the one you're currently using.
This won't work because esbuild is written with native code and needs to
install a platform-specific binary executable.

Specifically the "esbuild-darwin-arm64" package is present but this platform
needs the "esbuild-linux-arm64" package instead. People often get into this
situation by installing esbuild on Windows or macOS and copying "node_modules"
into a Docker image that runs Linux, or by copying "node_modules" between
Windows and WSL environments.

If you are installing with npm, you can try not copying the "node_modules"
directory when you copy the files over, and running "npm ci" or "npm install"
on the destination platform after the copy. Or you could consider using yarn
instead of npm which has built-in support for installing a package on multiple
platforms simultaneously.

If you are installing with yarn, you can try listing both this platform and the
other platform in your ".yarnrc.yml" file using the "supportedArchitectures"
feature: https://yarnpkg.com/configuration/yarnrc/#supportedArchitectures
Keep in mind that this means multiple copies of esbuild will be present.

Another alternative is to use the "esbuild-wasm" package instead, which works
the same way on all platforms. But it comes with a heavy performance cost and
can sometimes be 10x slower than the "esbuild" package, so you may also not
want to do that.


   at node_modules/esbuild/lib/main.js:1799

  1797 | `;
  1798 |           }
> 1799 |           throw new Error(`
       |                 ^
  1800 | You installed esbuild for another platform than the one you're currently using.
  1801 | This won't work because esbuild is written with native code and needs to
  1802 | install a platform-specific binary executable.

    at generateBinPath (/work/node_modules/esbuild/lib/main.js:1799:17)
    at esbuildCommandAndArgs (/work/node_modules/esbuild/lib/main.js:1875:33)
    at ensureServiceIsRunning (/work/node_modules/esbuild/lib/main.js:2040:25)
    at transform (/work/node_modules/esbuild/lib/main.js:1933:37)
    at transformWithEsbuild (file:///work/node_modules/vite/dist/node/chunks/dep-6b3a5aff.js:13325:30)
    at Object.transform (file:///work/node_modules/vite/dist/node/chunks/dep-6b3a5aff.js:13396:32)
    at transform (file:///work/node_modules/vite/node_modules/rollup/dist/es/shared/rollup.js:21928:16)
    at ModuleLoader.addModuleSource (file:///work/node_modules/vite/node_modules/rollup/dist/es/shared/rollup.js:22153:30)


  6 skipped
  1 error was not a part of any test, see above for details

To open last HTML report run:

  npx playwright show-report

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
āžœ  frontend git:(playwright-setup) āœ—