typescript not using semver, should peerDependencies be > instead of ^?

[fuxingloh]

🐛 bug report

With auto install, parcel attempts to download the typescript transformer this fails due to peer deps resolution. I use typescript 4.2.2 for my development, while peerDeps for the transformer package is set to ^3.0.0. This implies peer deps from 3.0.0 to 3.9.9, however typescript is not using semver and 4.0.0 is not a major release non a breaking change, so it should be >=3.0.0 instead?

Typescript is not using semver: microsoft/TypeScript#14116

parcel/packages/transformers/typescript-types/package.json

Lines 28 to 33 in 0a3b437

	"devDependencies": {
	"typescript": "^3.0.0"
	},
	"peerDependencies": {
	"typescript": "^3.0.0"
	}

🎛 Configuration (.babelrc, package.json, cli command)

{
  "devDependencies": {
    "@defichain/testcontainers": "0.0.0",
    "parcel": "2.0.0-nightly.620",
    "typescript": "4.2.2"
  }
}

🤔 Expected Behavior

Auto install should install without throwing peerDependencies error as typescript is not using semver.

😯 Current Behavior

Auto install fail if there is a conflicting peerDependencies. (Meanwhile, I force install with npm i --force and use --no-autoinstall)

💁 Possible Solution

Maybe use >=3.0.0 instead for all typescript peerDeps?

🔦 Context

💻 Code Sample

🌍 Your Environment

Software	Version(s)
Parcel	2.0.0-nightly.620
Node	v14.15.0
npm/Yarn	7.5.6
Operating System	MacOS