metamask / extensionizer

A JS module for writing cross-browser extensions

Built With:

• React
• Gatsby
• ❤️ from ConsenSys Digital Experiences Circle

🚀 Quick start

Ask @davidnguyen88 or @jlazoff for config files

1. Start it up

   git clone [email protected]:MetaMask/website.git
   yarn
   yarn develop

2. View site

   MetaMask is now running at http://localhost:8000!

   There is also a GraphQL API at http://localhost:8000/___graphql. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the Gatsby tutorial.

What's where?

Gatsby file structure documentation

.
├── public/
├── src/
    ├── components/
    ├── fonts/
    ├── fragments/
      ├──GraphQL_Documentation.md
    ├── images/
      ├── icons/
      ├── social-icons/
      ├── metamask-logo.svg
      ├── ...
    ├── lib/
      ├── theme.js
    ├── pages/
      ├── index.js
      ├── about.js
      ├── ...
    ├── html.js
├── gatsby-config.js
├── .env
├── GraphQL_Query_Documentation.md
├── package.json
└── README.md

Key Files

gatsby-config.js

The main configuration file for a Gatsby site. This is where you can specify information about your site (metadata), site title ,and description, which Gatsby plugins we are using, etc. (Check out the config docs for more detail).

src/fragments/ GraphQL query fragments that create standard data requests across components

src/lib/theme.js Contains styling constants for font sizes and weights, device sizes for media queries, shadows, and colors.

public/

Automatically generated output of gatsby build process for production.

src/pages

Files within this directory are turned into routes with the name of the file (e.g. about.js becomes /about). Only files within /pages are allowed to make dynamic GraphQL queries which cascade data down to components.

src/html.js Entry file used by Gatsby for all rendered pages html template

extensionizer's Issues

Add LICENSE file

This project is missing a license file

Migrate to extensionizer to typescript

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Use shared ESLint config

Migrate the project to use the shared ESLint config.

Rename to scoped package

Rename the published package to @metamask/extensionizer—this will allow org members to easily recognize 1st-party sources.

Should be compatible with mv3

from chrome, "New Manifest V2 extensions will no longer be accepted as of January 2022, and Manifest V2 will no longer function as of January 2023."

Update README to reflect Safari 14

As of Safari 14, Safari will offer Web Extensions—the README should be updated to reflect this information

Add CircleCI config

Add a CI config for consistency with the rest of the organization

Switch to Yarn

Migrate the project to Yarn for consistency with the rest of the organization.

Add CODEOWNERS file

This project is missing a CODEOWNERS file

extension.notifications is null when try to call extension.notifications.create

current installed version is 1.0.1
And I add "notifications" into permissions of manifest.json, I don't know why extension.notifications is null when call it in content_scripts

TODO: Deprecate in favor of webextension-polyfill

The webextension-polyfill project has similar goals to this project, and offers a nicer API. We should consider deprecating this project in favor of webextension-polyfill.

I'm not entirely sure the goals of the two projects are the same though, as they explicitly don't want to support non-standard features. If that's something we want, then maybe it's still worth maintaining this project.

---

Edit by @rekmarks: We are going to do this.