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.

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

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

Conversation

Robdel12
Copy link
Owner

@Robdel12 Robdel12 commented Dec 5, 2017

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.

Because distributing JS is so awesome & easy.
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 changed the title UMD module output UMD module output (Will fix #355) Dec 5, 2017
@Robdel12 Robdel12 merged commit 0c8dc3c into master Dec 5, 2017
@Robdel12 Robdel12 deleted the rd/umd-webpack-output branch February 7, 2018 03:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant