Should mount points take precedence in routing?

[winkler1]

Seems like if you have a mountpoint like _dist_ defined, it should have first crack at matching a request. Not have to be duplicated in the proxy logic.
Not a huge deal, but could save the user from some extra work and a potential footgun.

module.exports = {
  mount: {
    react: "/_dist_/" 
  },

  experiments: {
    routes: [
      {
        src: "/(?!_dist_|web_modules|__snowpack__).*"
        ...
      }
    ]
  }

[FredKSchott]

This used to be our default! But then it confused people who weren't expecting it. So now all aliases are opt-in, trading a line or two of extra config for less magic.

[winkler1]

Ha! That's hilarious. OK :)

[zanona]

I've noticed something similar where having two mount points as below, I would expect the second match rule would take precedence over the first one so /preview/Nav would render under the preview mount point, but it always falls back to /index.html

{
  mount: { public: "/", preview: "/preview" },
  routes: [
    { match: "routes", src: "/.*", dest: "/index.html" },
    { match: "routes", src: "/preview.*", dest: "/preview/index.html" },
  ],
}

Then following the example @winkler1 added I needed to define an exclusion on the first match which is not so intuitive

{
  mount: { public: "/", preview: "/preview" },
  routes: [
    { match: "routes", src: "/(?!preview).*", dest: "/index.html" },
    { match: "routes", src: "/preview.*", dest: "/preview/index.html" },
  ],
}