Closed jeffbl closed 2 years ago
The largest implications are likely (hat tip @JRegimbal for taking a brief look):
I also spent some time exploring this and i found out that a major dependency for v3 migration is https://github.com/parcel-bundler/parcel/issues/6079. We use parcel bundler to build our extension, and we may need to wait till parcel formally supports v3 manifest. The latest available version(2.3.2) of parcel does not support it yet.
Whether or not we know where later funding will come from, we should have a more solid plan/estimate for this work, even if it can't be done within the IGNIT timeframe.
As an update, it seems that parcel now supports building to v3 of the manifest based on this merged PR.
@jaydeepsingh25 unless something still pending, please close. Thanks!
We're using extension manifest v2. This gives an error when loading it unpacked manually, but should have no end-user implications for the rest of 2022. In January 2023, the extension will no longer operate, with a forced move to v3:
https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/
From a brief look, @JRegimbal indicates this is a non-trivial change that will require significant development effort.