-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
🐛 link to static html could'not be resolved, win10, parcel 1.0.3 #86
Comments
This issue is related to absolute paths. @lifeart if you're able to use relative paths, that should get you up and running until there is a fix (e.g. Issue is occurring in |
@brandon93s Do you wanna take this issue? |
Is this still a problem after #197 got merged? I think it should fix it, but I don’t have windows so I can’t test it. |
@dannify what if this file not exists on build time (html file link) ? |
Tested against current master; this is not fixed. |
Having the same problem with absolute paths in CSS files, which is a common approach to web development. Looking forward to PR #290 |
Same issue. Any reference to a static resource using a site root location fails with "Cannot resolve dependency" errors Examples CSS file HTML file |
@ajaymathur Hang tight, #290 will fix this issue once it get’s released :) |
@davidnagli seems like it's a bigger problem than expected |
So, we have two different approaches to basically the same problem: how to reference files starting at the root of a module. This issue proposes using absolute paths (e.g. |
for a "zero config" bundler, it ABSOLUTELY should handle absolute path correctly. There's no way around it. If you have to change your references to a breaking design, ie it won't run without being bundled, then you've lost the core argument for parcel. At least for the root of a project. I know the npm module thing is a concern, but you shouldn't have to change npm modules just to make their relative roots work either. |
@mix3d what would you expect |
I guess I'm not familiar enough with modules, but if I have an existing project who's / root is the root of the project, like how it would be served over http, that's how I'd expect it to work. I don't have to change anything between serving code as-is and bundling. Node module imports are clearly an issue though, because if they are referencing / as their module's root, things get tricky. How does webpack handle this? |
Right now Parcel cannot package a simple static site which uses nothing but html and some other assets which are referenced as site root "/" in either HTML or CSS. Shouldn't this be the simplest case and work forward from there. |
+1 |
Still getting this in 1.9.6 on first use. |
This is still an issue, no?
|
Add tracing measurements to phases in Parcel Approved-by: Niklas Mischkulnig Approved-by: Marcin Szczepanski
index.html
The text was updated successfully, but these errors were encountered: