nodejs
test: use unusual chars in the path to ensure our tests are robust
Hopefully our tests should work without assuming the repo is cloned in path that contains unusual chars.
TIL GNU Make does not support files containing whitespaces nor %, that's… unexpected.
Should we maybe avoid the hidden characters? I guess it's ok if GH only warns about them now but I don't want to see a permanent warning on the repo.
Should we maybe avoid the hidden characters? I guess it's ok if GH only warns about them now but I don't want to see a permanent warning on the repo.
I'm pretty sure it's just about the branch name for this PR, not related to the content of this PR.
console.log("\u2020\u00A3\u00A7\u2122" === '†£§™'); // true
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 88.54%. Comparing base (
48c75bc) to head (55edf5d). Report is 1237 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #48409 +/- ##
=======================================
Coverage 88.54% 88.54%
=======================================
Files 657 657
Lines 190395 190395
Branches 36552 36550 -2
=======================================
+ Hits 168580 168590 +10
+ Misses 14993 14986 -7
+ Partials 6822 6819 -3
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
- :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
![codecov[bot] avatar](https://avatars.githubusercontent.com/in/254?v=4 "Published by a pub.dev verified publisher"){kind=small}