To support yarn berry which had banned npm prepare script, I'd changed setup wizard of nestia to define npm postinstall script instead.
By the way, unlike the npm prepare script which works on only in the local drive and does not work when be installed from remote npm, npm postinstall script is working even when installing from the remote npm. Therefore, when publishing an npm module which has installed tyipa through setup wizard, it enforces users of derived libraries to run the npm postinstall command that requires ts-patch module.
To fix this crazy bug, I've decided to ban yarn berry on the setup wizard. From now on, when you run the npx nestia setup command, it will print a text that "yarn berry is not supported". If you still want to utilize the yarn berry, configure it manually by yourself please.
What's Changed
Full Changelog: v2.2.0...v2.2.1