Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix(mobx): Typescript pre-5.6 backwards compatibility #3960

Closed
wants to merge 5 commits into from

Conversation

tonyraoul
Copy link
Contributor

@tonyraoul tonyraoul commented Nov 15, 2024

Description

I've received some negative feedback w.r.t this patch #3935 mobx@6.13.4.
as it breaks typescript backwards compatibility with versions before 5.6.

Apologies for any inconveniences this has caused, as far as I understand typescript isn't pinned to a specific version by design hence the updates being reported as a patch within previous changes, I am not entirely sure if this changeset makes much sense to include within the mobx package or it would be preferable to start specifying peer dependencies for typing.

Alternatively you can use mobx@6.13.4+ with older typescripts versions by adding the attached .d.ts file to your project if you really need to type check dependencies.

Going to quote mwestrate here

It is not ideal, and generally I avoid this problem (many libs suffer from it) by slamming a skipLibCheck: true in my projects' tsconfig.

probably not worth it to add this patch but keen for feedback non the less.

Copy link

changeset-bot bot commented Nov 15, 2024

🦋 Changeset detected

Latest commit: 74bc622

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
mobx Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@tonyraoul
Copy link
Contributor Author

After some testing, I believe there is no value at all in shipping this vs using skipLibCheck: true
Going to close it for now, sorry for the noise.

@tonyraoul tonyraoul closed this Nov 16, 2024
@mweststrate
Copy link
Member

Yes, in general we just stick to TS latest since TS itself doesn't have any form of semantic versioning, so no worries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants