Граф коммитов

14 Коммитов

Автор SHA1 Сообщение Дата
Ben Bangert c28b061257
chore: update Node to LTS 20, TypeScript, tsconfig
Because:

* We want to update to Node 20 LTS.
* We want to target the JS output of Node 20.
* We want to use the latest TypeScript 5.4

This commit:

* Updates the Node version to 20 LTS.
* Updates the TypeScript version and related TS libs
  to 5.4.
* Updates tsconfig for the new Node 20 target.
2024-03-14 11:54:20 -07:00
Dan Schomburg 3f02bd5952
Revert "chore: update node to LTS 20" 2024-03-13 10:00:47 -07:00
Ben Bangert a022106a34
chore: update node to LTS 20
Because:

* We want to use the latest LTS version of node.

This commit:

* Updates the .nvmrc/Dockerfile and package.json
  files to use node 20.
2024-03-12 18:25:24 -07:00
Ben Bangert 6ed76a6caf
chore: update node to 18.18.2
Because:

* We want to use the latest security release of Node.

This commit:

* Updates Node.js to 18.18.2
2023-10-16 16:46:26 -07:00
Ben Bangert 54f0c2e7a2
chore: update to TS to 5.2.2 and Node to 18.17.1
Because:

* We want to use the latest typescript features.

This commit:

* Updates to TypeScript 5.2.2.
* Updates to Node 18.17.1 as OOM would occur frequently with 18.14.
* Updates CI to use a large instance with increased memory for Node.
2023-08-28 14:47:29 -07:00
Barry Chen da11e63832
chore(deps): upgrade to node.js 18
Because:
 - we want to use the latest node LTS major version

This commit:
 - upgrades FxA to use node 18, with two workarounds
   - Webpack uses a hash algorithm that's no longer supported by default
     in node 17+, causing build failures; --openssl-legacy-provider is
     used as the workaround
   - dns.lookup in node 17+ by default returns the results in the same
     order as they are from the resolver, which could lead to
     'localhost' resolving to ::1; --dns-result-order=ipv4first is used
     as the workaround
2023-03-20 13:28:10 -05:00
Danny Coates 17e06a38d2
chore(node): upgrade to node 16 (#10799) 2021-10-22 16:10:22 -07:00
Ben Bangert f7a05aa57d
fix: update nvmrc to match needed node version
Because:

* It's useful for scripts that check nvmrc on directory change to see
  when the projects needed node version has changed.

This commit:

* Updates nvmrc to precisely match the needed node that is also checked
  when starting up all the services.
2020-12-01 09:17:48 -08:00
Danny Coates 8fafe2468a
fix(dev): updated .nvmrc to 14 2020-10-30 09:50:38 -07:00
Jody Heavener b3107169e7
chore(node): Update .nvmrc to use Node v12, to match requirement in _scripts/check.sh 2020-02-15 13:13:55 -05:00
Vlad Filippov 746c91d545 Switch .nvmrc to 10 2019-03-18 15:49:18 -04:00
Vlad Filippov 98afff665f feat(node): update nvmrc to node 8 2018-04-23 20:50:00 -04:00
Shane Tomlinson 1f749ebf1a feat(node): upgrade to Node 6 mozilla/fxa-local-dev#90) r=vladikoff 2017-07-14 13:45:45 -04:00
Udara Weerasinghege 2e9956352f feat(config): add nvmrc file for easier nvm use mozilla/fxa-local-dev#88) r=vladikoff 2017-05-29 15:41:11 -04:00