Tom Chen

I believe it's due to their WebWorker API. Would you look at their docs too?

@chibicode I think so. You can load Prism that way and use `expose` loader in conjunction with it to make `Prism` globally accessible. In that case, you don't need to...

@schickling could you try the latest example that's loading prism from cdn (not webpack)? https://github.com/tomchentw/react-prism/blob/cde34385be8ac5792d6974c115d2b731a8ce58c5/index.html#L11

Did your console has errors?

Depending on which `ToastMessageFactory` you're using. If you use `ReactToastr.ToastMessage.animation` like in the [example](https://github.com/tomchentw/react-toastr/blob/master/examples/gh-pages/scripts/ReactRoot.js#L6), then no jquery is needed.

We could have our own file in this repo. Say: `src/toastr-responsive.css`, and our user can import it via: ``` css @import url(~toastr/toastr.min.css); @import url(~react-toastr/lib/toastr-responsive.css); ```

The lodash issue can be fixed by using `babel-plugin-lodash`. Does anyone want to create a PR to fix this?

I think it's reasonable for a library to put `react` as peerDeps in this case. Putting them in deps might generate two or more versions of React and it's always...

I noticed that you're talking about `devDependency`. Interesting. Does it really make sense to put a strong dependency like React in `devDependency`?

@SonyaOrlova would you please turn on **Allow edits from maintainers**? Thanks