18 Commits

Author SHA1 Message Date
Matt Godbolt
3aeed42066 Upgrade to node 20 minimum, target node 22 (#7343)
Co-authored-by: Mats Jun Larsen <mats@jun.codes>
2025-02-18 12:43:21 -06:00
Sam James
19440e35e3 etc: find-node: use command -v, not which (#6567)
`which` isn't in POSIX and some Linux distributions (e.g. Debian,
Gentoo) are trying to remove it from their base installs. See
https://lwn.net/Articles/874049/.
2024-06-08 15:30:59 -05:00
Matt Godbolt
5d776aaae3 Replace ts-node-esm with direct calls to node to support node 20 (#5521)
- works both v18 and v20
- see https://github.com/TypeStrong/ts-node/issues/1997
2023-09-27 21:57:18 -05:00
Matt Godbolt
fb4b7bb16e Bump used node version to 18 (#4778)
Still assume node 16 compatibility for now.
2023-02-25 12:43:00 -06:00
Matt Godbolt
bfa10e7afa Set our minimum node to 16 (#4005)
See #3995, seems we can't install on lower node any more?
2022-08-30 10:08:44 -05:00
Matt Godbolt
eabfdca2fc Bump to new LTS version 16 node 2022-01-10 22:38:43 -06:00
Matt Godbolt
dc1592cdc1 Update to node v14.18.0 (#3026)
* Update to node v14.18.0
2021-10-11 23:18:19 -05:00
Austin Morton
044dcfbf88 Use ES6 Modules (#2132) 2020-09-26 16:59:26 -04:00
Matt Godbolt
17e7f85d7a async aws; note that we're now using node 11 features 2020-01-14 22:06:04 -06:00
RabsRincon
77568f747b Simplify version checks 2019-12-23 09:52:59 +01:00
Rubén Rincón
f2e1384ea0 Add more descriptive messages to find-node script 2019-12-20 10:54:34 +01:00
Rubén Rincón
dc789ea9a6 Allow node verisons > 8, but recommend latest LTS 2019-12-20 10:45:30 +01:00
Rubén Rincón
4a3cd05ca0 Bump node version to LTS v12 2019-12-20 10:13:22 +01:00
Marc Poulhiès
b145fd6564 Do not use system node by error
If system's node is overriden by something in PATH, having NODE_DIR
empty will cause the script to still use node found in /bin/.
Only consider the first case if NODE_DIR is not empty.
2019-04-30 15:04:28 +02:00
RabsRincon
47b65b15d9 Upgrade to latest Node LTS (10) 2019-04-12 15:32:31 +02:00
Ruslan Garipov
42c9b269f0 Make ``find'' scripts compatible w/ the Bourne sh
By default FreeBSD does not have the Bourne-again shell (Bash)
installed.  Therefore, the system fails to execute two ``find'' scripts
(etc/scripts/find-node and etc/scripts/find-yarn) running by the
Makefile within the `.node-bin` and `.yarn-bin` targets.

I see nothing Bash-specific in those scripts.  Also I believe that
`[[ expression ]]` commands in those particular cases can be safely
replaced with the `test` built-in commands.

With these changes I can now run a local ``Compiler explorer'' instance
on FreeBSD.

Signed-off-by: Ruslan Garipov <ruslanngaripov@gmail.com>
2019-01-31 20:24:00 +05:00
Matt Godbolt
d92ef4f2b6 Prevent creation of an empty .node-bin or .yarn-bin if the version check fails. Helps with #850 2018-03-05 08:14:17 -06:00
Matt Godbolt
f8468e5d92 Use a local-installed yarn. Refactor all the 'find node' stuff out of the Makefile 2018-02-10 17:10:56 -06:00