Skip to content

fix: revert import config module as data#13731

Merged
patak-cat merged 2 commits intomainfrom
fix/revert-import-config-module-as-data
Jul 6, 2023
Merged

fix: revert import config module as data#13731
patak-cat merged 2 commits intomainfrom
fix/revert-import-config-module-as-data

Conversation

@patak-cat
Copy link
Member

Description

Fixes #13730. See issue for description. If we want to move forward with using data:text/javascript, we would need to consider more edge cases. I think reverting is the best move right now.


What is the purpose of this pull request?

  • Bug fix
  • New Feature
  • Documentation update
  • Other

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@patak-cat patak-cat added the p4-important Violate documented behavior or significantly improves performance (priority) label Jul 6, 2023
@patak-cat patak-cat merged commit b0bfa01 into main Jul 6, 2023
@patak-cat patak-cat deleted the fix/revert-import-config-module-as-data branch July 6, 2023 14:11
@silverwind
Copy link

silverwind commented Jul 6, 2023

Should re-open these:

#13267
#9470

@patak-cat
Copy link
Member Author

Done, thanks @silverwind!

@silverwind
Copy link

Thanks, could you also unlock the discussions in them?

@s10y10
Copy link
Contributor

s10y10 commented Jul 7, 2023

I'm sorry for the situation, let's find a better way

@patak-cat
Copy link
Member Author

Dont worry @s10y10, it was good we tried the approach.

@silverwind
Copy link

silverwind commented Jul 7, 2023

I think the revert was premature, the issue should have been analyzed at least.

#13730 did not provide a reproduction, so we will never know what the actual issue was (strictly speaking, the issue is invalid because it has no reproduction).

Maybe the URL was somehow incorrectly encoded, e.g. stuff that good test coverage can catch.

@patak-cat
Copy link
Member Author

@silverwind I think the revert was valid here, we weren't sure this approach was safe and it failed as soon as we released it, and seems the issue is on our side. We can try with more time again. I hope @cpojer could provide a minimal reproduction to help you test a new take at it.

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

Labels

p4-important Violate documented behavior or significantly improves performance (priority)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[4.4.0] "Invalid URL" error with dynamic imports in plugins.

4 participants