Parcel --public-url ./ doesn't support scripts and links in subfolders

[advename]

🐛 bug report

I have following file tree:

│   index.html
│
├───donate
│       step-1.html
│       step-2.html
│
├───scripts
│       main.js
│
└───styles
        main.css

The step-1.html and step-2.html are both linking to the main.js and main.css. In order to get to that path I have to use ../scripts/main.js and ../styles/main.css to access them. But when bundling them with parcel using following command parcel build index.html --public-url ./ , parcel bundles the output as if they are in the same folder. Anchor tags, however, are working fine.

🎛 Configuration (.babelrc, package.json, cli command)

Zero config

🤔 Expected Behavior

Parcel should bundle to the correct paths

😯 Current Behavior

Parcel bundles to the root path for scripts and links

💻 Code Sample

A full working example can be seen here:
https://github.com/advename/Parcel-error-example/tree/master

🌍 Your Environment

Software	Version(s)
Parcel	1.9.7
Node	8.11.2
npm/Yarn	5.6.0
Operating System	Windows 10 64-bit Pro

[kirillrogovoy]

Is it a bug or a feature?

Parcel bundles all your Javascript and CSS into separate files and places them near the processed HTML file.

It replaces all the references in your script and link tags so that they point to the correct files.

So what's the original problem you're trying to solve? All you Javascript and CSS should be working just fine.

---

On a separate note, it's important to understand that the output bundles (e.g. index.css) or not 1:1 to the input assets.

You could have ten different <link> tags and you would still end up with just one output file.

[DeMoorJasper]

If you require the same asset from 2 different places, parcel creates a shared bundle for both these files. Not sure why you wouldn’t want this though as it would save you or your company a bit of money and your users loading time. As there is only one bundle that needs to get cached at the cdn and user.

In Parcel 2 we’ve taken this a big step further with extracting shared assets into shared bundles. (As most applications share a couple libraries across various entrypoints)

_{Sent with GitHawk}

[advename]

It's not about feature or "best practice" in this case.
In the code sample that I've provided, you can clearly see in the dist that parcel links to <link rel="stylesheet" href="main.04aee6b8.css"> but since I'm using apache and this project is in a subfolder, well, the correct path should be <link rel="stylesheet" href="../main.04aee6b8.css">. The same goes for the script element.

[DeMoorJasper]

@advename ow alright, will flag it as a bug again.

[mischnic]

In the code sample that I've provided, you can clearly see in the dist that parcel links to <link rel="stylesheet" href="main.04aee6b8.css"> but since I'm using apache and this project is in a subfolder, well, the correct path should be <link rel="stylesheet" href="../main.04aee6b8.css">. The same goes for the script element.

That reminds me of #1801 / #2518

[hugojing]

Would someone like to tell us about the progress?

[yisar]

I have the same problem. What can I do now?

[WireCrazii]

This bloody bug still exists.

[gswierczynski]

Is there a way to work around this?
I am using static-i18n to generate localized versions of html file.
I would like to have each language version in /<language_code>.
Unfortunately all parent ".." paths are ignored and output files in subdirectories reference assets without them.

[alsoknownasdrew]

Any updates on this?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.