You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm WARN [email protected] requires a peer of eslint@^4.9.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of eslint@^4.9.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] No repository field.
npm WARN [email protected] license should be a valid SPDX license expression
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
audited 11059 packages in 7.017s
found 7 high severity vulnerabilities
run `npm audit fix` to fix them, or `npm audit` for details
The text was updated successfully, but these errors were encountered:
I tried gitpod and met another issue, but I don't have the bandwidth to fix it recently, PR is welcomed.
UnhandledPromiseRejectionWarning: Error: Unable to start Chrome. If you have the DEBUG env variable set,there will be more in the logs.
at /workspace/cloudquery/node_modules/@serverless-chrome/lambda/dist/bundle.cjs.js:376:13
at Generator.throw (<anonymous>)
at step (/workspace/cloudquery/node_modules/@serverless-chrome/lambda/dist/bundle.cjs.js:311:193)
at /workspace/cloudquery/node_modules/@serverless-chrome/lambda/dist/bundle.cjs.js:311:404
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:1724) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:1724) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Get an error when the gitpod is launched
The text was updated successfully, but these errors were encountered: