Was this PR even reviewed? It broke our app. Thanks! smh

How? Any reproductions?

How? Something was there. You removed it. Yes, the slash seemed extraneous, but I've got to imagine we aren't the only ones who had a process that took its existence into account. These are the kinds of changes that make people nervous about upgrading. Luckily, we were able to track it down and apply a fix.

I'm very sorry for the inconvenience caused by this commit.

In theory, the old behavior is undocumented, unintended, and non-intuitive, so I didn't expect it to be depended on by any project.

And we've put this in the beta channel for 18 days before a stable release, so I really didn't intend it to break any production app. I'm deeply sorry for that.

Anyway, in retrospect,

1. Such insignificant fixes should be included in a major release rather than a patch, considering every bug fix could be a breaking change to some users.
2. I'm considering using the ~ version range for generated projects by default in the next major (or maybe minor, I haven't discussed with other team members yet) version of Vue CLI.
   Only fixes for regressions can be added to subsequent patch releases.
   Other bug fixes should be included in minor versions, and users need to run vue upgrade manually to upgrade.

What do you think?

Thankfully, it didn't break the production app. We caught it in our CI environment. It just caused a bit of panic as we scrambled to understand what had changed.

We accidentally deleted package-lock.json all of sudden our web app stopped to work! We then finally found it was because we didn't add leading '/' our vue.config.js

I didn't update vue-cli, so which package was changed by this ?

My second question is what about the '/' in the end ? The document here https://cli.vuejs.org/config/#publicpath seems to say we need the '/' in the end. But thru our test we found we don't.