On PR code update

chore(parser): mark parser as GA #2692

Sign in to view logs

Triggered via pull request July 25, 2024 08:22

dreamorosi

synchronize #2831

chore/parser_ga

Status Success

Total duration 2m 17s

Artifacts –

pr-run-linting-check-and-unit-tests.yml

on: pull_request

run-unit-tests / check-layer-publisher

run-unit-tests / check-docs-snippets

run-unit-tests / check-docs

Matrix: run-unit-tests / check-examples

Matrix: run-unit-tests / run-linting-check-and-unit-tests-on-utilities

Annotations

6 errors

run-unit-tests / check-docs-snippets

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './envelope.js'?

run-unit-tests / check-docs

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './envelope.js'?

run-unit-tests / check-layer-publisher

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './envelope.js'?

run-unit-tests / check-examples (app)

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './envelope.js'?

run-unit-tests / run-linting-check-and-unit-tests-on-utilities (20)

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './envelope.js'?

run-unit-tests / run-linting-check-and-unit-tests-on-utilities (18)

Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './envelope.js'?