Skip to content

Conversation

@akrawitz
Copy link
Contributor

This is a second attempt to close #2078 (with #2079 being the first attempt).

The issue is that an absolute Windows path prefixed with a null byte is not a valid absolute file path, but it is (apparently) a valid URL (the null byte gets eaten as white space, and then the C: is interpreted as the URL scheme). However, in the context of processing Rollup plugins, the null byte is a signal that this path should be treated in a special way.

This fix explicitly checks for the null byte to avoid this issue, as discussed with @giamir and @43081j.

@changeset-bot
Copy link

changeset-bot bot commented Jan 17, 2023

🦋 Changeset detected

Latest commit: 712e5fa

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@web/dev-server-rollup Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rollup adapter is not resolving virtual modules correctly in windows environments

2 participants