Skip to content

lib folder shouldn't be in repo, it should be a part of the pre publish npm commands #4

@sankho

Description

@sankho

I wrote this before I was a bit more aware of owning a public NPM module.

The lib folder represents the converted ES5 assets, necessary for working w/n browsers. It is the resulting output of the npm run build command. Rather than being manually run before every commit, it really should just be part of the pre publish script that is run whenever a subscriber runs npm install on their own package.json file. Less work, more of the current standard.

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