Skip to content
This repository was archived by the owner on Aug 4, 2021. It is now read-only.
This repository was archived by the owner on Aug 4, 2021. It is now read-only.

path.resolve in createFilter #20

@pjordaan

Description

@pjordaan

Hi, I want to know what is the reason to do a path.resolve in createFilter as it gives trouble for me.
I have written a custom rollup resolve plugin (it's closed source) that resolves (virtual) source files without a full path, but I can't make it work with other rollup plugins because of this path.resolve.

The problem is that the glob will include the working directory, because of the path.resolve, but I do not expect this behaviour.

I expect that calling someRollupPlugin({ include: ['**/*.js']}) to include would result in the use of the match '**/*.js' and not the match '/projects/my-working-directory/**/*.js'

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions