Unity has adopted my package! 🎉
Published on March 3, 2022 by Kalle Fagerberg
I have held communication with some Unity developers almost since the dawn of this project. It has taken 3 years, and now Unity has officially adopted the responsibility of the Newtonsoft.Json fork.
The state of Unity's package
Their package is a fork (of my fork) of Newtonsoft.Json. This means, that from now on, when using their package instead of mine you will still get:
- The `Newtonsoft.Json.Utilities.AotHelper` type I forked from SaladLab that has been a core part of this fork since the get-go.
- All my IL2CPP and managed code stripping specific bugfixes.
- Continue to use an up-to-date fork of Newtonsoft.Json, but now kept up-to-date by Unity employees instead of me.
- Also, it's practically always included in newer versions of Unity as many of Unity's internal packages depend on it, so you probably don't even have to install it any more!
The latest version of their package containing Newtonsoft.Json v13.0.1 can be found here: https://docs.unity3d.com/Packages/[email protected]/manual/index.html
At the time of writing (2022-03-03) it is still marked as hidden inside the official UPM registry, but I've added documentation in the wiki on how to install this newer hidden version here: https://github.com/jilleJr/Newtonsoft.Json-for-Unity/wiki/Install-official-via-UPM
At the time of writing (2022-03-03) it is still marked as hidden inside the official UPM registry, but I've added documentation in the wiki on how to install this newer hidden version here: https://github.com/jilleJr/Newtonsoft.Json-for-Unity/wiki/Install-official-via-UPM
The future of my project
It is now marked as deprecated. What this means practically for my package is:
- No more bug fixes
- No more added features
- No more new documentation
- I'm disabling the ability to donate/sponsor
- My existing Cloudsmith packages will still be available
- My GitHub releases will still be available, for those that rely on Git-based UPM package imports
- I will keep on responding to issues and discussions, but they will get even less priority from my other hobby projects. For ensured support regarding Newtonsoft.Json in Unity (from Unity employees), please use any of the following pages instead:
The future of my converters package
It will keep on living. That package will continue to get bug fixes and added features as they are discovered or requested.
Unity has no plans of adopting that one as well, as it's much more of an extension in nature. However, the same was said about my Newtonsoft.Json-for-Unity fork to begin with as well, so who know? Maybe in ~3 years more they will? Though it's much more probably they've gotten up-to-date with the latest .NET versions by then to start relying on System.Text.Json instead.
Unity has no plans of adopting that one as well, as it's much more of an extension in nature. However, the same was said about my Newtonsoft.Json-for-Unity fork to begin with as well, so who know? Maybe in ~3 years more they will? Though it's much more probably they've gotten up-to-date with the latest .NET versions by then to start relying on System.Text.Json instead.
Huge thanks to all supporters!
From the bottom of my heart, thank you so dearly to everyone who has donated throughout the years! ♥