named imports under v8

[perrin4869]

Hi, I've been using this lib importing stringify and parse by name, import { stringify, parse } from 'query-string' under v7, but on v8 this is not possible anymore. On v7 this worked thanks to static parsing of the commonjs module.
I tried to add support for this to send a PR, but the linter doesn't like that there are both named exports and default exports with stringify and parse properties, so this would mean a huge refactor.
Was wondering if you intend to support this, or if this usage is deprecated?
Thanks!

[sindresorhus]

I don't intend to support this. I don't like named exports when the named imports have too generic names. parse could be anything. If I were to support named export, I would rename all the exports, and I don't want to make such a big breaking change and I also don't have time to decide on new names. I'm using ESM exports to create the default export, so tree shaking should still work even when it's a default export.

[perrin4869]

Well, they have generic names but they are imported from query-string so it is not ambiguous at all what they are used for. An end-user can rename if they choose or they can import * from "query-string"...

[sindresorhus]

In large files, the import can be far away from where it's actually used. A user could indeed rename, but it's not a good API design to force the user to rename to a better name themselves.