Skip to content

Drop bower support and remove compiled code from source control #23

@timwis

Description

@timwis

Including dist makes it inconvenient to submit pull requests -- the submitter isn't sure whether to include it in the PR, and the author has no insight into whether the new compiled file accurately reflects the latest source code. I think instead we'd run the build command during npm publish. The gh-pages branch also needs it for the demos, so we could use travis to compile and push from the master branch to gh-pages.

This would probably mean bower no longer works, though, as there's no compiled version sitting on github. Do people still use bower? Any other advantages to having the built file in source control?

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