metamask-extension/app/manifest/v2/chrome.json

{
  "content_security_policy": "frame-ancestors 'none'; script-src 'self'; object-src 'self'",
  "externally_connectable": {
    "matches": ["https://metamask.io/*"],
    "ids": ["*"]
  },
  "minimum_chrome_version": "80"
}
Build system refactor (#8140) * build - start static asset task cleanup * build - simplify manifest tasks * build - refactor + rename some tasks * build - various cleanups * manifest - fix ref from controller * build - drop gulp for simple async tasks * build - breakout gulpfile into multiple files * build - rename some tasks * build - use task fn refs instead of string names * build - bundle all scripts first, except for contentscript * build - improve task timeline * deps - update lock * build - improve task time printout * build/scripts - remove intermediate named task * build - use 'yarn build' for task entry points * build - properly run tasks via runTask for timeline display * development/announcer - fix manifest path + clean * build - lint fix * build - make all defined tasks possible entry points * build/task - properly report errors during task * ci - fix sesify/lavamoat-viz build command * build/scripts - run each bundle in separate processes * lint fix * build - forward childProcess logs to console * build/task - fix parallel/series stream end event * build/scripts refactor contentscript+inpage into a single task * build/static - use the fs for 150x speedup zomg * lint fix * build/static - fix css copy * Update development/build/scripts.js Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * Update development/build/scripts.js Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * Update development/build/index.js Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * deps - remove redundant mkdirp * deps - remove unused pumpify * deps - remove redundant merge-deep * deps - prefer is-stream of isstream * deps - remove clone for lodash.cloneDeep * clean - remove commented code * build/static - use fs.copy + fast-glob instead of linux cp for better platform support * build/manifest - standardize task naming * build/display - clean - remove unused code * bugfix - fix fs.promises import * build - create "clean" as named task for use as entrypoint * build/static - fix for copying dirs * Update development/build/task.js Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * Update development/build/display.js Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * Update development/build/display.js Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * Update development/build/display.js Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * build - use task refs, tasks only return promises not streams, etc * lint fi bad merge + lint * build - one last cleanup + refactor * build - add comments introducing file * build/manifest - fix bug + subtasks dont beed to be named * Update package.json Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * build/task - remove unused fn * Update package.json Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * Update development/build/styles.js Co-Authored-By: Mark Stacey <markjstacey@gmail.com> * Update development/build/styles.js Co-Authored-By: Mark Stacey <markjstacey@gmail.com> Co-authored-by: Mark Stacey <markjstacey@gmail.com> 2020-03-09 01:55:02 +01:00			`{`
Restore support for Chromium v78 (#17251) Support has been restored for Chromium v78. Previously the extension would crash upon startup. The main incompatibility was the use of ES2020 operators (the optional chain and nullish coalesce operators) in the libraries `@ethereumjs/util` and `superstruct`. This was resolved by transpiling those libraries. After fixing that, the extension no longer crashed but the UI refused to connect. This was because the UI process was not being identified as an internal process, because the code responsible for checking that was relying on the `origin` property of `MessageSender` [1] which wasn't added until Chromium v80. The check has been updated to use the `url` property instead, which existed in older versions of Chrome. Lastly, the content security policy was updated to include the default content security policy alongside the intended modification. Newer versions of Chrome will merge the configired CSP with the default, but older versions required it to be explicitly specified. This should not result in any functional change. [1]: https://developer.chrome.com/docs/extensions/reference/runtime/#type-MessageSender 2023-01-23 17:06:48 +01:00			`"content_security_policy": "frame-ancestors 'none'; script-src 'self'; object-src 'self'",`
Move `externally_connectable` from base to Chrome manifest (#9824) The `externally_connectable` property of the extension manifest is not recognized by Firefox. It has been moved from the base manifest to the Chrome manifest, so that we no longer get a warning about this property on Firefox. We would like to eventually remove it from the Chrome manifest as well, but we'll wait until we can batch it with other permission changes so that it doesn't unnecessarily re-prompt the user (see #9804) 2020-11-09 14:51:09 +01:00			`"externally_connectable": {`
			`"matches": ["https://metamask.io/*"],`
			`"ids": ["*"]`
			`},`
Revert "Fix(18190): add tabs to permission when initializing app (#18218)" (#18336) This reverts commit 1eb102fd964952d5d2b9a53070b0c868cbfe59bd. 2023-03-29 21:11:08 +02:00			`"minimum_chrome_version": "80"`
Use `prettier` for JSON linting (#9396) Instead of using `eslint-plugin-json` for linting JSON files, `prettier` is now used. `prettier` is capable of detecting and correcting more problems than `eslint-plugin-json` can, such as indentation. All JSON files have been run through `prettier`. The changes are all superficial. 2020-09-11 15:57:39 +02:00			`}`