Seat 285

[tevo-nikita-ivashkov]

Jira: SEAT-285

Why / What

This PR:

• updates dependencies
• converts repo to monorepo
• switches build tooling to tsup and changes package structure
• adds ts definitions to package build
• fixes tests for new version of react
• extracts usage examples into separate packages
• introduces CI pipelines with auto publish from main branch through changesets.

Testing

I tested this code by running unit tests.

Reviewer Checklist (To be edited and marked by approver)

After approving the PR, the reviewer should check the boxes below. See the Reviewer Checklist company standard for more info on these bullet points.

• Do you understand the reasoning behind the need for the changes?
• Given only new or existing tests*, do you feel confident that all changes work as intended and solve the problem at hand?
• Are all success and failure paths accounted for in the tests? If not, are the omissions explained/justified?
• If coverage ignores are present, is justification provided inline (or linked to) or is a link to a ticket to address in the future provided?
• Are you willing to accept the same responsibility for this code as the author?

*If existing tests, requester should point out what applies

PR Code Coverage

• Changeset: XX%
• Overall: XX%

Measure with bin/test_cov or some other means. You can find html coverage levels in coverage/index.html or in stdout.

After a successful test run, you can also see calculated and merged coverage, per branch, on Grafana

[coneybeare]

I changed the action to dynamically generate a one-time use token

[coneybeare]

Working on adding npm token as well

[coneybeare]

Ok, npm account recovered, updated, and token generated. Stored under TEVO_NPM_TOKEN

[tevo-vladislavkozak]

I think it's better to use single quotes instead of double ones throughout the project like we do it in the Shell project. Anyway it's a minor comment

[tevo-andrei-lukin]

I think better use same prettier configs in all projects

[tevo-nikita-ivashkov]

I've tried to limit style changes compared to the previous version, but I agree with you guys on the consistency argument.
Will change the prettier config in a separate PR.

[tevo-andrei-lukin]

Its hard to properly review all of that, but surface level looks good, only minor complains about prettier settings.