Skip to content

Consider using a non-default context for build actions #494

@jrburke

Description

@jrburke

It seems like more people are using requirejs to load modules but also do an optimization at the same time in node. The build's use of the default context is making this awkward, comes with a hidden gotcha.

See if it can just use its own specific context instead.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions