| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Review requested:
|
Sorry, something went wrong.
|
This isn't right, process.features.typescript will check whether the currently running process supports typescript, not whether the executable does. The correct value to check would be process.config.variables.node_use_amaro |
Sorry, something went wrong.
Codecov ReportAll modified and coverable lines are covered by tests ✅ Additional details and impacted files @@ Coverage Diff @@
## main #55320 +/- ##
==========================================
- Coverage 88.39% 88.39% -0.01%
==========================================
Files 652 652
Lines 186777 186777
Branches 36039 36039
==========================================
- Hits 165109 165100 -9
- Misses 14917 14927 +10
+ Partials 6751 6750 -1 |
Sorry, something went wrong.
|
We might want fix the commit message as well s/when amaro unavailable/when Amaro is unavailable/. |
Sorry, something went wrong.
I figured this out (which is why I changed the state back to draft). Currently running tests locally (both with and without amaro) before pushing up the correction. |
Sorry, something went wrong.
|
also should actually set process.features.typescript to false if amaro is not loaded |
Sorry, something went wrong.
|
Can you rebase? |
Sorry, something went wrong.
👍. Will do so once the linter failure on main is fixed. |
Sorry, something went wrong.
Fix two tests that fail when `node` is configured `--without-amaro`.
Rebased. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Fix two tests that fail when `node` is configured `--without-amaro`. PR-URL: #55320 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Chemi Atlow <chemi@atlow.co.il> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
| Back | FazBrowse Home | New Git URL |
Fix two tests that fail when node is configured --without-amaro.