You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This project uses [Conventional Commits](https://www.conventionalcommits.org/) for automated versioning and releases. When making commits, please follow this format:
4
+
5
+
-`feat:` for new features (triggers minor version bump)
6
+
-`fix:` for bug fixes (triggers patch version bump)
7
+
-`BREAKING CHANGE:` for breaking changes (triggers major version bump)
8
+
-`docs:`, `style:`, `refactor:`, `test:`, `chore:` for other changes (no version bump)
9
+
10
+
Examples:
11
+
12
+
```text
13
+
feat: add support for new login form
14
+
fix: resolve virtual keyboard detection issue
15
+
docs: update installation instructions
16
+
```
17
+
18
+
Releases are automatically created when changes are pushed to the main branch using semantic-release.
Copy file name to clipboardExpand all lines: README.md
+14-10Lines changed: 14 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,10 +7,14 @@ Removes the annoying (and arguably useless from a security standpoint) virtual k
7
7
You can download the latest release for:
8
8
9
9
-**Firefox** from [Firefox Add-ons](https://addons.mozilla.org/en-US/firefox/addon/jsc-unlocker/)
10
-
-**Chrome** from the [Chrome Web Store](https://chromewebstore.google.com/detail/jsc-unlocked/ekeehglopcojnbieeopijckckabkpbfj).
11
-
-**Safari**, I won't be paying the 100$/year fee that Apple requires to publish on their store. **See the next section for instructions on how to build the extension yourself from the source code here.** Then lookup how to load a local extension into Safari.
10
+
11
+
-**Safari**, I won't be paying the 100$ _per year_ fee that Apple requires to publish on their store. **See the next section for instructions on how to build the extension yourself from the source code here.** Then search for how to load a local extension into Safari.
12
+
13
+
-**Microsoft Edge**, the partner center page to become an extension publisher is currently broken, as is common in these sluggish Microsoft developer dashboards. I have tried opening a support ticket but I get sent to a useless AI system that repeats the same steps and won't let me speak to a human. **See the next section for instructions on how to build the extension yourself from the source code here.** Then search for how to load a local extension into Edge.
14
+
12
15
-**Opera** from [Opera Add-ons](https://addons.opera.com/en/extensions/details/jsc-unlocker/).
13
-
-**Edge** from the [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons/detail/jsc-unlocker).
16
+
17
+
-**Google Chrome** from the [Chrome Web Store](https://chromewebstore.google.com/detail/jsc-unlocked/ekeehglopcojnbieeopijckckabkpbfj).
14
18
15
19
## Development 🛠️
16
20
@@ -28,11 +32,11 @@ _With all requirements ready:_
28
32
npm install
29
33
```
30
34
31
-
- Continue to the next step if you want to alter the extension code. If you just want to build it run:
35
+
- Continue to the next step if you want to alter the extension code. If you just want to build it, run the respective script:
32
36
33
37
```shell
34
38
npm run build
35
-
# The output will be in the `.output` folder!
39
+
# The results will be in the `.output` folder!
36
40
```
37
41
38
42
- To see live changes _(hot reload)_ when the extension code is updated, start a development session, which will automatically open a configured browser window. Refer to the `scripts` field in the `package.json` file for more details:
@@ -43,14 +47,14 @@ _With all requirements ready:_
43
47
npm run dev:safari
44
48
```
45
49
46
-
- Note that the **Chrome** version of the extension will also work in**Edge** and **Opera**, as these share the same browser engine, **Chromium**. This applies to any other _Chromium-based_ browser as well. Same goes forthe **Firefox** version, which will also workin all _Firefox-based_ browsers.
50
+
- Note that the **Google Chrome** version of the extension is the same one used for**Edge** and **Opera**, as these share the same browser engine, **Chromium**. This applies to any other _Chromium-based_ browser as well. Same goes for the **Firefox** version, which will also workin all _Firefox-based_ browsers.
47
51
48
-
#### Tooling 🧰
52
+
### Tooling 🧰
49
53
50
-
- Biome is used as a linter and formatter:
54
+
- Biome is used as a linter _and_ formatter:
51
55
52
56
```shell
53
-
npm run check
57
+
npm run lint
54
58
```
55
59
56
60
- After running `npm install` pre-commit hooks will be automatically installed to format code before a commit. If for some reason the hooks do not install correctly, instal them manually using:
@@ -59,4 +63,4 @@ _With all requirements ready:_
59
63
npx lefthook install
60
64
```
61
65
62
-
- When using pre-commit hooks, git commands will fail ifany files are checked with errors. Changed files must be added to the staged area and commited again to apply fixes
66
+
- See also the [CONTRIBUTING.md](./CONTRIBUTING.md) guidelines ifyou plan on contributing to the project.
0 commit comments