|
1 |
| -This is a [Plasmo extension](https://docs.plasmo.com/) project bootstrapped with [`plasmo init`](https://www.npmjs.com/package/plasmo). |
2 |
| - |
3 |
| -## Getting Started |
4 |
| - |
5 |
| -First, run the development server: |
6 |
| - |
7 |
| -```bash |
8 |
| -pnpm dev |
9 |
| -# or |
10 |
| -npm run dev |
11 |
| -``` |
12 |
| - |
13 |
| -Open your browser and load the appropriate development build. For example, if you are developing for the chrome browser, using manifest v3, use: `build/chrome-mv3-dev`. |
14 |
| - |
15 |
| -You can start editing the popup by modifying `popup.tsx`. It should auto-update as you make changes. To add an options page, simply add a `options.tsx` file to the root of the project, with a react component default exported. Likewise to add a content page, add a `content.ts` file to the root of the project, importing some module and do some logic, then reload the extension on your browser. |
16 |
| - |
17 |
| -For further guidance, [visit our Documentation](https://docs.plasmo.com/) |
18 |
| - |
19 |
| -## Making production build |
20 |
| - |
21 |
| -Run the following: |
22 |
| - |
23 |
| -```bash |
24 |
| -pnpm build |
25 |
| -# or |
26 |
| -npm run build |
27 |
| -``` |
28 |
| - |
29 |
| -This should create a production bundle for your extension, ready to be zipped and published to the stores. |
30 |
| - |
31 |
| -## Submit to the webstores |
32 |
| - |
33 |
| -The easiest way to deploy your Plasmo extension is to use the built-in [bpp](https://bpp.browser.market) GitHub action. Prior to using this action however, make sure to build your extension and upload the first version to the store to establish the basic credentials. Then, simply follow [this setup instruction](https://docs.plasmo.com/workflows#submit-your-extension) and you should be on your way for automated submission! |
| 1 | +This is a [Plasmo extension](https://docs.plasmo.com/) project bootstrapped with [`plasmo init`](https://www.npmjs.com/package/plasmo). |
| 2 | + |
| 3 | +## Getting Started |
| 4 | + |
| 5 | +First, run the development server: |
| 6 | + |
| 7 | +```bash |
| 8 | +pnpm dev |
| 9 | +# or |
| 10 | +npm run dev |
| 11 | +``` |
| 12 | + |
| 13 | +Open your browser and load the appropriate development build. For example, if you are developing for the chrome browser, using manifest v3, use: `build/chrome-mv3-dev`. |
| 14 | + |
| 15 | +You can start editing the popup by modifying `popup.tsx`. It should auto-update as you make changes. To add an options page, simply add a `options.tsx` file to the root of the project, with a react component default exported. Likewise to add a content page, add a `content.ts` file to the root of the project, importing some module and do some logic, then reload the extension on your browser. |
| 16 | + |
| 17 | +For further guidance, [visit our Documentation](https://docs.plasmo.com/) |
| 18 | + |
| 19 | +## Making production build |
| 20 | + |
| 21 | +Run the following: |
| 22 | + |
| 23 | +```bash |
| 24 | +pnpm build |
| 25 | +# or |
| 26 | +npm run build |
| 27 | +``` |
| 28 | + |
| 29 | +This should create a production bundle for your extension, ready to be zipped and published to the stores. |
| 30 | + |
| 31 | +## Submit to the webstores |
| 32 | + |
| 33 | +The easiest way to deploy your Plasmo extension is to use the built-in [bpp](https://bpp.browser.market) GitHub action. Prior to using this action however, make sure to build your extension and upload the first version to the store to establish the basic credentials. Then, simply follow [this setup instruction](https://docs.plasmo.com/workflows#submit-your-extension) and you should be on your way for automated submission! |
0 commit comments