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
Missing license #93
Comments
Thank you! The PR has been merged. Is there a plan for a patch release here ? |
Is there some development here ? Would it be possible to release 3.0.1 with the license ? We are currently blocked on using node-sass because of this small inconvenience. |
Published 3.0.1
…On Wed., 10 Oct. 2018, 1:36 am Vladimir Gorej, ***@***.***> wrote:
Is there some development here ? Would it be possible to release 3.0.1
with the license ? We are currently blocked on using node-sass because of
this small inconvenience.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#93 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjZWKTVt8xtY0J4-v-ds73mg6tZ43GNks5ujLRcgaJpZM4W3QCK>
.
|
Thank you very much. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, is it possible to incorporate the LICENSE file inside the repo and npm package ? Now it's missing. It's implied by MIT license that if licensed under the MIT the source code must be accompanied by full license text. If the license file is not in the repo nor npm package the code is proprietary and the world cannot use it.
Thank you
The text was updated successfully, but these errors were encountered: