Skip to content

Resolver perf: Prefer Maps over dynamic objects for normalised exports field (5/n) #113

Resolver perf: Prefer Maps over dynamic objects for normalised exports field (5/n)

Resolver perf: Prefer Maps over dynamic objects for normalised exports field (5/n) #113

Triggered via pull request August 27, 2024 16:39
Status Failure
Total duration 1m 34s
Artifacts

build-test-and-deploy.yml

on: pull_request
Matrix: test
Type check, lint, smoke test
38s
Type check, lint, smoke test
Tests with coverage
1m 25s
Tests with coverage
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
test (ubuntu-latest, 18.0) / Tests [Node.js 18.0, ubuntu-latest]
Process completed with exit code 1.
Type check, lint, smoke test: packages/metro-transform-plugins/src/addParamsToDefineCall.js#L26
Always use `== null` or `!= null` to check for `null` AND `undefined` values (even if you just expect either of them). Within fb we treat them as equal and `== null` checks for both