Skip to content

Unexpected module.exports, please use export default instead #15

@tonimedina-pri

Description

@tonimedina-pri

I was wondering if you could add support to "export default".
That way this package will also compile on the client side.
The way it is right now (module.exports) crashes IE11.
Thanks in advance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions