Skip to content

Commit ffc4344

Browse files
committed
More meta
1 parent 4ddbf3d commit ffc4344

File tree

21 files changed

+105
-31
lines changed

21 files changed

+105
-31
lines changed

docs/en/_meta.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
},
77
{
88
"text": "Blog",
9-
"link": "/blog/index",
9+
"link": "/blog",
1010
"activeMatch": "/blog"
1111
}
1212
]

docs/en/blog/announcing-2-0-0-alpha.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Extension.js is all about making cross-browser extension development as easy as
88

99
Since being [featured on HackerNews](https://hnrankings.info/40210627/), we've made a lot of internal improvements to make the package smaller, faster, and more developer-friendly.
1010

11-
To me, "very easy" means very low cognitive effort. It means something is familiar. Developers are familiar with copy/paste, and as a developer myself, it feels very easy if I can copy/paste code and have an instant response of what the code means without configuration. Even if the code is not understandable at first, a fast visual response is a clear indicator of how things are expected to work. That's the expectation of Extension.js v2: something very easy to work with.
11+
To me, "very easy" means very low cognitive effort. It means something is familiar. Developers are familiar with copy/paste, and as a developer myself, it feels very easy if I can copy/paste code and have an instant response of what the code means without configuration. Even if the code is not understandable at first, a fast visual response is a clear indicator of how things are **expected** to work. That's the expectation of Extension.js v2: something very easy to work with.
1212

1313
**Version 2.0.0-alpha**
1414

@@ -21,6 +21,8 @@ To me, "very easy" means very low cognitive effort. It means something is famili
2121

2222
The alpha release is focused on bug fixes and testing all existing features while we finish the documentation and templates websites. Keep an eye on this blog or follow us on X for future updates.
2323

24+
For the next release, we are going to focus on making all the existing features stable enough to document and test.
25+
2426
Thanks for reading. Talk soon.
2527

2628
Cezar Augusto<br/>

docs/en/blog/announcing-2-0-0-beta.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,21 @@
66

77
Extension.js is now officially in beta.
88

9+
Beta comes to stabilize the features introduced in the alpha release and to fix all known issues with the browser compatibility.
10+
911
**Version 2.0.0-beta**
1012

1113
- Fixed SASS Modules not working in the content script.
1214
- Add support to Svelte templates.
1315
- Add preview command.
16+
- Add universal support for content_scripts (via hard-reload and hot-reload).
17+
- Fix all known browser issues for Firefox, Edge, and Chrome.
1418
- Updated documentation (this one!)
1519

1620
The beta release is focused on making all the existing features stable enough to document and test. New features are locked until the next stable release and the documentation is now up-to-date. This is the last beta release before the release candidate.
1721

22+
For the next release, we are going to focus on shaping Extension.js into a faster and smaller bundle that can work both locally and remotelly (via `pnpm dlx`, `yarn dlx`, and of course `npx`).
23+
1824
Thanks for reading. Talk soon.
1925

2026
Cezar Augusto<br/>

docs/en/blog/index.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Latest News
22

3+
Follow the latest news and updates from the team at Extension.js! Here, you will find information about new releases, features, and more. For the latest updates, we are also available on [Twitter](https://twitter.com/extension_js) and [Discord](https://discord.gg/extensionjs).
4+
35
## [Announcing v2.0.0-beta](/blog/announcing-2-0-0-beta)
46

57
> October 18, 2024

docs/en/docs/commands/dev.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,8 +52,8 @@ Below is a breakdown of the available flags for the `dev` command:
5252
| `--polyfill` | Boolean | Enables compatibility for the `browser.*` API in Chromium-based browsers | `false` |
5353
| `--profile` | Profile path | Specifies a path to a browser profile for testing | `default` |
5454
| `-b, --browser` | Browser to run the extension | Specifies the browser to run (`chrome`, `edge`, `firefox`, `all`) | `"chrome"` |
55-
| `--chromium-binary` | Path to the Chromium binary | Provides the path to a custom Chromium-based browser binary [Read more](../browsers/running-other-browsers.mdx) | `undefined` |
56-
| `--gecko-binary` | Path to the Gecko binary | Provides the path to a custom Gecko-based browser binary [Read more](../browsers/running-other-browsers.mdx) | `undefined` |
55+
| `--chromium-binary` | Path to the Chromium binary | [Provides the path to a custom Chromium-based browser binary](../browsers/running-other-browsers.mdx) | `undefined` |
56+
| `--gecko-binary` | Path to the Gecko binary | [Provides the path to a custom Gecko-based browser binary](../browsers/running-other-browsers.mdx) | `undefined` |
5757
| `--starting-url` | URL | Starting URL for testing with the extension | `chrome://newtab` |
5858
| `--open` | Boolean | Whether or not to automatically open the browser upon starting dev | `true` |
5959

docs/en/docs/commands/preview.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,8 +45,8 @@ In this example, the extension is created in the `path/to/my-extension` director
4545
| [path or url] | The extension path or the remote extension URL | If a path is defined, previews the local extension. If a URL is provided, pulls the extension from remote source and previews it as a local extension | `process.cwd()` |
4646
| `--profile` | Profile path | Specifies a path to a browser profile for testing | `default` |
4747
| `-b, --browser` | Browser to run the extension | Specifies the browser to run (`chrome`, `edge`, `firefox`, `all`) | `"chrome"` |
48-
| `--chromium-binary` | Path to the Chromium binary | Provides the path to a custom Chromium-based browser binary [Read more](../browsers/running-other-browsers.mdx) | `undefined` |
49-
| `--gecko-binary` | Path to the Gecko binary | Provides the path to a custom Gecko-based browser binary [Read more](../browsers/running-other-browsers.mdx) | `undefined` |
48+
| `--chromium-binary` | Path to the Chromium binary | [Provides the path to a custom Chromium-based browser binary](../browsers/running-other-browsers.mdx) | `undefined` |
49+
| `--gecko-binary` | Path to the Gecko binary | [Provides the path to a custom Gecko-based browser binary](../browsers/running-other-browsers.mdx) | `undefined` |
5050
| `--starting-url` | URL | Starting URL for testing with the extension | `chrome://newtab` |
5151

5252
## Examples

docs/en/docs/development/_meta.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@
44
{ "name": "css", "label": "CSS" },
55
{ "name": "javascript", "label": "JavaScript" },
66
{ "name": "background", "label": "Background Scripts / Service Worker" },
7-
{ "name": "content_scripts", "label": "Content Scripts" },
7+
{ "name": "content-scripts", "label": "Content Scripts" },
88
{ "name": "locales", "label": "Locales" },
99
{ "name": "json", "label": "JSON" },
1010
{ "name": "icons", "label": "Icons" },
11-
{ "name": "web_accessible_resources", "label": "Web Accessible Resources" }
11+
{ "name": "web-accessible-resources", "label": "Web Accessible Resources" }
1212
]
File renamed without changes.
File renamed without changes.

docs/en/docs/getting-started/templates.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ When you run the `create` command with the `--template` flag, Extension.js fetch
2121

2222
## More templates
2323

24-
You can find a list of all officially supported templates [here](https://github.com/extension-js/extension.js/tree/main/examples). Their folder name is the template param name like so, `--template=<folder_name>`.
24+
You can find a [list of all officially supported templates here](https://github.com/extension-js/extension.js/tree/main/examples). Their folder name is the template param name like so, `--template=<folder_name>`.
2525

2626
## Best Practices
2727

0 commit comments

Comments
 (0)