Skip to content

there is no need to wrap bundle #34

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

Merged
merged 1 commit into from
Aug 24, 2015
Merged

there is no need to wrap bundle #34

merged 1 commit into from
Aug 24, 2015

Conversation

wenbing
Copy link
Contributor

@wenbing wenbing commented Aug 21, 2015

No description provided.

@joeybaker
Copy link
Contributor

👍

@joshwnj
Copy link
Member

joshwnj commented Aug 24, 2015

Thanks @wenbing ! This is definitely a more "proper" way to use browserify :) Then only question in my mind is that previously, the bundle callback would only be called after the css file has finished writing. With these changes that order may be different, right?

I'm not sure if that's going to cause any issues but at this stage I'm happy to go ahead and accept this PR, and fix any issues that arise. @joshgillies can you think of any reason this shouldn't be merged?

@joshgillies
Copy link
Member

This has bugged me for some time. Looks solid! 👍

Merging!

joshgillies added a commit that referenced this pull request Aug 24, 2015
Remove wrapped browerify bundle function
@joshgillies joshgillies merged commit aeea32e into css-modules:master Aug 24, 2015
@riophae
Copy link

riophae commented Aug 25, 2015

Awesome!

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.

5 participants