Commit fec45b3a authored by Philip Chimento's avatar Philip Chimento 🚮

Update README instructions

Update the instructions to reflect that we have more than one migration
tool now.
parent e1fdf4f3
🛠 moz60tool 🛠
===============
🛠 mozjs-deprecation-tools 🛠
=============================
This is a tool for checking your JS source code to see if you are using
any Mozilla-specific extensions that will be removed in SpiderMonkey 60.
This is a set of tools for checking your JS source code when you upgrade
to the next extended-support release (ESR) of SpiderMonkey, to see if
you are using any Mozilla-specific extensions that will be removed.
To run it:
- Upgrading from ESR 52 to ESR 60? Use `moz60tool`.
- Upgrading from ESR 60 to ESR 68? Use `moz68tool`.
To run it (replace `moz60tool` with whichever one you are using):
```
./moz60tool myfile.js
```
......@@ -19,10 +23,13 @@ The tool is only intended to be used once, at the time when you migrate
your codebase.
It's not meant for use in CI pipelines.
Oh no, my distro has already upgraded to GJS with SpiderMonkey 60
-----------------------------------------------------------------
As a workaround, it _should_ work to run the tool with the `js52` binary
which is probably shipped with your SpiderMonkey 52 devel package:
Oh no, my distro has already upgraded to GJS with the new SpiderMonkey
----------------------------------------------------------------------
As a workaround, it _should_ work to run the tool with the JS
development shell binary which is probably shipped with the devel
package from the previous SpiderMonkey ESR.
In the case of `moz60tool`, that would be the `js52` binary shipped with
whatever your distro's equivalent of `mozjs52-devel` is.
```
js52 ./moz60tool myfile.js
```
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment