Version Packages (#6089) #18395
jnsdlsCI.yml
on: push
optimize_ci
3s
Build Packages
51s
Lint Packages
1m 51s
Unit Tests
5m 19s
Size
0s
Matrix: E2E Tests
Annotations
2 errors and 11 warnings
|
Unit Tests
***#test: command (/home/runner/work/js/js/packages/***) /home/runner/setup-pnpm/node_modules/.bin/pnpm run test exited (1)
|
|
Unit Tests
Process completed with exit code 1.
|
|
optimize_ci
Request body: {"token":"***","caller":{"name":"graphite-ci-action","version":"0.0.0"},"context":{"kind":"GITHUB_ACTIONS","repository":{"owner":"***-dev","name":"js"},"sha":"1cff849b697773eb1ed686e9b3259d9a55aa71b0","ref":"refs/heads/main","head_ref":"","run":{"workflow":"CI","job":"optimize_ci","run":13023414921}}}
|
|
optimize_ci
Response status: 400
|
|
optimize_ci
***-dev/js/undefined
|
|
optimize_ci
Response returned a non-200 status. Skipping Graphite checks.
|
|
Lint Packages:
apps/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L163
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L170
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L177
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/minting/TransactionResults.tsx#L161
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/minting/TransactionResults.tsx#L168
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/minting/TransactionResults.tsx#L175
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/minting/erc1155-mint-to.tsx#L267
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|