Parcel: Client side routing with multiple entrypoints

[atrauzzi]

🐛 bug report

(I think this problem description is simple enough that the full template is a bit overkill.)

I'm running with multiple entrypoints on the dev server, when an HMR reload is triggered, I get a 404 because it attempts to resolve the exact path (something like /myapp.html/some/route) rather than simply serving /myapp.html and allowing the client-side routing to take over for the /some/route portion.

Is this supported currently?

[devongovett]

Please fill out the template. It's useful to know e.g. your parcel version and other things asked in the template.

[atrauzzi]

It's a simple enough question, consider this question applicable to all versions of Parcel or the current, whichever bypasses the bureaucracy.

There's literally zero nuance.

[DeMoorJasper]

Client side routing is supported by default?

Not entirely sure what the real bug is, unless you haven't actually tried it yet.

[atrauzzi]

For multiple entrypoints?

[DeMoorJasper]

Not for multiple entrypoints, at least not on Parcel 1.

In Parcel 2 it can fallback to index.html, client side routing usually only really happens for spa's and once you have multiple entrypoints you really no longer have an spa

[atrauzzi]

That seems like an arbitrary principle.

I have multiple SPAs (login + signup, consent screens, app itself)

Could it not be possible to always serve entrypoints when they are explicitly in the path?

[DeMoorJasper]

I've never seen anyone do that before but sure it's possible

[atrauzzi]

Well, currently it's not as parcel won't redirect to entrypoints when there are multiple.

I don't think it's at all unusual to need this. All applications can benefit from reusing the things they have in common.

[DeMoorJasper]

I meant it's technically possible and can be added to parcel not that it's currently possible without using a seperate dev server.

Anyway gonna flag this as a feature