ts-node | TypeScript execution and REPL for node.js | Runtime Evironment library

Most probably an issue with SSL. For me it was the pass phrase in the SSL key.

As I researched a lot and did not find a solution to this issue as it's occurring only on the newer version of the animation package.

I tried the below versions:

• 13.2.4 (Latest one) throwing same es error

• 13.2.3 throwing same es error

• 13.2.2 throwing same es error

• 13.2.1 throwing same es error

• 13.2.0 working without error.

So I think for a temporary fix you should update your package.json by pointing to a specific version of this npm like below.

You need to add "compat" like this

I finally found the root cause! OpenSea expects a public property called name in order to display the proper Name of the Collection instead of a static label Unidentified contract.

I came across this while looking at their reference code (which depends on a now 3-year-old MultiToken-Contract implementation and needs all in all some downgrades of Node and other tools in order to get it build [a downgrade to Node 10 worked best for me today] ).

From v13 angular doesn't use tslint anymore due to deprecation.

Run ng add @angular-eslint/schematics to add eslint to your application.

It will use tslint-to-eslint-config to migrate you to eslint automatically.

It will generate a .eslintrc.json file and migrate tslint.json to it.

Nothing else is needed to be done.

Here's a hypothesis (that can be experimentally proven).

The difference in behavior between good and bad can be explained by the order of awaits.

In bad you're awaiting on throwError after you have awaited on doSomething, while in good, you're awaiting on Promise.all, which will not return until both are fullfilled or at least one is rejected (which will be the case here).

So in bad, the throwing is happening outside of await, and your catch is not triggered, and it is caught internally by node.

If you change your bad so that you await on throwError first, then your catch will get triggered:

I do not understand why the first git status in the before_script already gives me a detached head.

I think the pipeline creates a detached repository by initial fetching.

You are right, GitLab CI does checkout a specific commit as opposed to a certain branch. You could however add git checkout "$CI_COMMIT_REF_NAME" to your before_script:

This error should be resolved after specifying the latest version of the

• firebase-functions, v3.16.0, and

• firebase-functions-test, v0.3.3.

I was able to fix the issue by following this guide in the documentation.

This example is copy-pasted from the documentation