Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

UMD module output (Will fix #355) #357

Merged
merged 2 commits into from
Dec 5, 2017
Merged

UMD module output (Will fix #355) #357

merged 2 commits into from
Dec 5, 2017

Commits on Oct 20, 2017

  1. Have webpack output the module dance. 

    Because distributing JS is so awesome & easy.
    @Robdel12
    Robdel12 committed Oct 20, 2017
    Configuration menu
    Copy the full SHA
    9d6a8a3 View commit details
    Browse the repository at this point in the history

Commits on Dec 5, 2017

  1. Fix #355 by distributing with umd 

    This didn't work simply by making the `outputTarget: "umd"` because I
had two entries in the webpack config file. One scss and one JS. Which
threw webpack for a loop I'm guessing.

By breaking the CSS & JS complies into their own webpack files I can
now consume dropkick in other applications just fine.
    @Robdel12
    Robdel12 committed Dec 5, 2017
    Configuration menu
    Copy the full SHA
    931f109 View commit details
    Browse the repository at this point in the history