feat: allow components to provide absolute import path

[antfu]

This would allow libraries to provide absolute import paths (from library submodules, or virtual modules) using the components:extend hook. In my case, I am integrating with unplugin-icons.

[pi0]

I think it should still work by setting a relative path to node_modules. Are you using a virtual import pattern? An example would be nice :)

[pi0]

We would need to normalize windows paths in fullPath condition

[antfu]

The import for unplugin-icons uses something like import Icon from '~icons/logos/nuxt-icon', which in the original behavior it will always prepend with ../ and got this error:

See unplugin/unplugin-icons#63 for the implementation.

This other case I can think about might be importing from some libraries, like: import Button from 'element-ui/lib/button'

As for the windows path resolution, I guess since the isAbsolute can only be provided by hooks, we can leave the responsibility to the module author?

[pi0]

I'm mostly hesitating to see if we really need another component option or can actually fix the situation by default. For resolving ~, for instance we can check prefix to disable resolution on virtual and ~, @.

This other case I can think about might be importing from some libraries, like: import Button from 'element-ui/lib/button'

This case makes sense. But maybe with a flag like resolvePath: false ?

One more point, we usually allow inherit options from dirOptions (apply option to a group of scanned components) (unplugin/unplugin-icons#63 (comment))

[antfu]

Do you mean we rename isAbsolute to resolvePath?

[pi0]

Yes please, and also auto-enable the flag when ~, @ prefixes was provided if possible :)

[jd-solanki]

Sorry guys I don't want to disturb you here but I guess this is stale for a long time. Will this get updated?

Actually, I am waiting for this PR unplugin/unplugin-icons#63

Regards.

[AqueleHaru]

Still waiting too.