-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem writing a resolver that resolves Http Urls #205
Comments
@llacroix Sorry for delay, do you have problems? |
enhanced-resolve only handles resolving on fs. URL resolving would be handled on webpack side. Maybe you want to specify |
@evilebottnawi I did work around a few bugs and it's working much better than when I wrote that. I'll post an updated version tomorrow. Back story for this extension if it wasn't clear: As far as I remember, the only I had was related to the production release. I'm not sure I fixed that and somehow assets would work in development builds but not in production builds. Thanks anyway for answering. |
Here:
|
Here's what I have so far:
It does get a few urls that starts with
http
orhttps
. But when it fetch and resolve a file containing an import as such:It doesn't even trigger an new request. In theory, I could track the actual parent path and compute the actual path to download but for some reasons, it simply fail to resolve with something like this:
But '/-/@pika/[email protected]...' is relative to an url and not the path. How do I tell the resolver to not check for the path I resolved for the previous file?
The text was updated successfully, but these errors were encountered: