Copyright in production build about classnames HOT 2 CLOSED

Hi @astrauka,

This was added explicitly in response to #28 so that the license is preserved when you ship classnames with your app.

I believe this is similar to other packages you may include with licenses (e.g. React, etc)

According to the license, you must preserve the copyright when including the code in your app, however if you handle this separately with regards to crediting OSS packages in your project I'm happy for you to deal with that however you like for minified code :)

However, this is code that's taken a nontrivial amount of time to develop & maintain so I do appreciate the credit as a minimum in return.

from classnames.

Thank you for the answer :) what I just noticed is that I am separating code to vendor and app bundles and all the libs should go to bundle, but classnames got into app. So that was the actual issue. Will profile produced JS to figure out how to put the package next to other vendor assets.
And the trick is to add 'classnames/bind' instead of 'classnames' to vendor bundle entries.

from classnames.