Skip to content

option { includesOnly: true } leaves @nomangle directive in place causing syntax error  #63

Description

@felixniemeyer

While developing setting includesOnly: true in the glsl loader options is great help.

I am using a @nomangle directive.
This works fine, when not setting includesOnly true, meaning, when all default minifying and processing is turned on.

When I switch to my development webpack config that has includesOnly set to true, shader compilation fails because the @nomangle directive is left in place.

Error when compiling shader: ERROR: 0:160: '$' : invalid character
ERROR: 0:160: 'nomangle' : syntax error

I imagine a solution would be to update includesOnly mode to still handle @nomangle directives by simply dissolving them.

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