chore: remove integration tests

[timofei-iatsenko]

Description

I tried to fix "integration" tests and then decided to completely remove them. "integration" taken in quotes, because it's actually not an integration tests. It is the same test but executed on the compiled output. This doesn't have much sense now and bring more maintenance burden for us.

The unbuild is responsible to validate correctness of entrypoints in the package.json. And the way how we consume packages in tests is as close as possible to real use case with compiled packages, so we are more than on the safe side in this regard.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Examples update

Fixes # (issue)

Checklist

• I have read the CONTRIBUTING and CODE_OF_CONDUCT docs
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation (if appropriate)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
js-lingui	✅ Ready (Inspect)	Visit Preview	Jan 16, 2025 11:07am

[github-actions]

size-limit report 📦

Path	Size
packages/core/dist/index.mjs	2.91 KB (0%)
packages/detect-locale/dist/index.mjs	618 B (0%)
packages/react/dist/index.mjs	1.37 KB (0%)

[timofei-iatsenko]

Unblocking pipeline from integration tests revealed a problem with typings. I did a fixin this PR, but wondered why it wasn't caught during tsd tests. I dug into tsd setup and found that our setup is obsolete. tsd-lite we use is deprecated and archived. The proposed alternative is https://tstyche.org/

Also with a newer version of tsd / tsd-lite and stricter checks it started complaining about ramda types, so i decided to put an effort to get rid of it.

I will do migration to tstyche in next PRs