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
Note that `--engines=all` does not install the `v8-debug` binaries.
113
113
114
+
## Installing specific versions
115
+
116
+
jsvu also supports installing specific versions alongside the main engine binaries (which it keeps up to date). Here’s an example:
117
+
118
+
```sh
119
+
jsvu v8@7.2.502
120
+
```
121
+
122
+
Binaries installed using this method are named `${BINARY}-${VERSION}`, so that the above example installs a binary named `v8-7.2.502`. This way, there’s never any conflict with the main `v8` binary, which jsvu can keep up to date.
123
+
124
+
This feature works for all the supported engines:
125
+
126
+
```sh
127
+
jsvu chakra@1.11.6
128
+
jsvu javascriptcore@242640
129
+
jsvu spidermonkey@66.0b13
130
+
jsvu v8@7.2.502
131
+
jsvu v8-debug@v7.1.302
132
+
jsvu xs@8.7.0
133
+
```
134
+
135
+
If you pass in an invalid version number, or if the JavaScript engine creators don’t provide a precompiled binary for that specific version, jsvu shows an error.
136
+
137
+
As a shorthand, for `v8` and `v8-debug` builds, jsvu can even figure out the last known good revision within a [milestone](https://v8.dev/docs/version-numbers). To install the latest available V8 v7.2.x for example, run:
138
+
139
+
```sh
140
+
jsvu v8@7.2
141
+
# jsvu figures out that this means v7.2.502, and then installs that version.
142
+
```
143
+
114
144
## Security considerations
115
145
116
146
_jsvu_ avoids the need for `sudo` privileges by installing everything in `~/.jsvu` rather than, say, `/usr/bin`.
0 commit comments