Valentin Oliver Loftsson

I got the same error using `v-for` on `` and using `data-section-selector`. A fix that worked for me was to use `` tags and the `href` attribute, although not ideal....

Regardless of the frontend framework, you need to explicitly provide the routes in the plugin configuration. If you have dynamic routes, you could fetch the routes from your API before...

Yes, you can. But you need to know the routes in advance since the `routes` options only accepts an Array. It really depends on where you store the route information....

Could you run the two configs separately in sequence? For instance, with NPM ``` "scripts": { "build:prerender": "webpack --config-name-1 && webpack --config-name-2" } ``` ?

I was using serve for my SPA until I couldn't anymore because I need to proxy to API server. I found that [local-web-server](https://github.com/lwsjs/local-web-server) seems to support a lot of scenarios...

It could be done very simplisticly by checking if the first character of `url` is the forward slash. If it is, then prepend `window.location.origin` to the given `url`. That would...

As you said yourself, I'm also not sure if this is documented behavior. I tested it on the new chromium-based Edge desktop browser. There, the protocol and host are prepended...

I don't think there is an option for that. As [you can see here](https://github.com/on2-dev/share-api-polyfill/blob/43c8bf027a51660a661cca03b8fca9b1cde32e87/src/share.js#L6) the polyfill is a fallback to `navigator.share`. So if `navigator.share` exists, then the browser's implementation is...

The Web Share feature in recent Edge and Chrome versions for Windows also appeared to me as really limited, there doesn't seem to be an option for sharing on social...

You might be able to do ```js navigator.share = undefined ``` before importing the polyfill.