Skip to content

Support traditional user scripts with @include/@match #27

@westonruter

Description

@westonruter

I found myself putting all of the behaviors needing to be applied globally into the one default.js. This caused the file to get quite messy; same goes for sites that I have multiple independent user scripts that I want to get applied. I would prefer to be able to stick traditional *.user.js files into my ~/.js directory and have their @include/@match metadata checked against the requested domain to determine whether they get concatenated in the response.

In addition to passing the domain to the local web server, perhaps the entire URL should then be passed so that user scripts can match more granularly at the path level, not just by domain.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions