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
{{ message }}
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.
I've just added nodejs/node#35477 to the agenda which is new WhatWG URL resolution changes.
I'm temporarily blocking that as it has effects on the modules system.
As an example, we have the following before and after:
newURL('////path/to/file.js','file:');// Before the PR -> file:///path/to/file.js// After the PR -> file:////path/to/file.js
This in turn may affect module registry identity as the same module could be loaded twice in this way (if it were imported via import '///path/to/file.js' and import '/path/to/file.js' say).
It would be useful to discuss some of these cases further before landing there.
The text was updated successfully, but these errors were encountered:
I'd note that this does impact other areas like policies and whatever decisions we make should likely be documented and agreed upon across the whole project.
I've just added nodejs/node#35477 to the agenda which is new WhatWG URL resolution changes.
I'm temporarily blocking that as it has effects on the modules system.
As an example, we have the following before and after:
This in turn may affect module registry identity as the same module could be loaded twice in this way (if it were imported via
import '///path/to/file.js'
andimport '/path/to/file.js'
say).It would be useful to discuss some of these cases further before landing there.
The text was updated successfully, but these errors were encountered: