You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Turbopack build: Fix node-file-trace test (#77641)
### What?
- Changed the ES5-Ext module path from `es5-ext/array/#/clear.js` to
`es5-ext/array/of/index.js` in the test fixture
- Updated corresponding test assertions to match the new module path
- Modified runtime detection in API tests to support both webpack and
Turbopack runtime patterns
- Fixed console error usage in test to use require('console').error
- Updated Turbopack build tests manifest to mark "should output traces"
test as passing
Turbopack failed to detect `#` folders, likely because it treats it like
a hash regardless of `/#/`. I've created a new issue for this to track
it. It's not a blocker for what this test is checking for.
### Why?
This PR fixes the "should output traces" test that was previously
failing in the Turbopack build tests. The changes ensure proper module
path resolution and test assertions that work with both webpack and
Turbopack runtimes.
### How?
- Updated the module import path in the test fixture
- Adjusted test assertions to match the new module path
- Added regex patterns to support both webpack and Turbopack runtime
files
- Fixed console error usage to ensure proper error reporting
- Updated the test manifest to reflect the now passing test
0 commit comments