Closed twschiller closed 8 months ago
I can work on this if you'd like
- Can we close out?: Identify gaps preventing migration to Chrome Manifest V3 #287
I think to do that we need to actually run the extension in MV3 and see what's still broken (which I assume it's still a bit and likely more than before, namely data that is not in storage.session)
@fregante I think @grahamlangford is creating the build today
I think to do that we need to actually run the extension in MV3 and see what's still broken (which I assume it's still a bit and likely more than before, namely data that is not in storage.session)
I started a PR with a lint rule here: https://github.com/pixiebrix/pixiebrix-extension/pull/7180
Looks like there are at least a couple places that need to be migrated. Could you take a look?
I can work on this if you'd like
@fregante I think @grahamlangford is creating the build today
If you've got the extra bandwidth, that would be a big help. I've got a lot of meetings today, and I'll be out next week. I'd like to get this in sooner rather than later.
@fregante reopening because the build is not working correctly:
See screenshot the build-production-3
is still manifest v2:
While we're fixing this, let's also improve the naming: https://github.com/pixiebrix/pixiebrix-extension/issues/7196
Is there a number vs. string issue?: https://github.com/pixiebrix/pixiebrix-extension/blob/35019bf89b4566c2835209b25f2ef22d95df76c5/webpack.config.js#L416-L416
Context
Implementation Sketch
Definition of Done
GOOGLE_*
env variablesDiscussion
GOOGLE_*
environment variablesRelated Code