-
ie. For MV3, I need: I tried:
|
Beta Was this translation helpful? Give feedback.
Answered by
aklinker1
Oct 15, 2023
Replies: 1 comment 1 reply
-
The manifest option only accepts actual manifest schemas, so having a If you need to customize the manifest per build target, you should set it equal to a function to return the manifest depending on the manifest version of the build: // wxt.config.ts
export default defineConfig({
manifest: ({ manifestVersion }) => {
const permissions = ["storage", "nativeMessaging"];
if (manifestVersion === 2) permissions.push("*://*/*", "<all_urls>");
else permissions.push("scripting");
return {
permissions,
},
},
} I was going to link the config reference, but the type listed there is wrong... I'll get that fixed. Created #173 for updating it. |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
aklinker1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The manifest option only accepts actual manifest schemas, so having a
mv2
andmv3
fields won't do anything.If you need to customize the manifest per build target, you should set it equal to a function to return the manifest depending on the manifest version of the build:
I was going to link the config reference, but the type listed there is wrong... I'll get that fixed. Created #173 fo…