Hi, at first, your project is awesome, i'm using it in several projects and its always a good time when working with it.
But sadly i discovered last week that the project is using a package which uses a package with a LGPL license, that means i can not use inqurier any more as long as it has the external-editor package which uses the jschardet package, (the jschardet package has the LGPL license)
That means btw you can only publish your software as MIT as long as the external-editor package is not substantially impare inquirer. :/
Do you think it's possible to replace the external-editor package? Or maybe check out if it's ok to use MIT for this project, i'm not a lawyer, so it's possible i'm wrong.
Seems to not be a problem according to this answer https://softwareengineering.stackexchange.com/questions/141847/how-does-using-a-lgpl-gem-affect-my-mit-licensed-application and the details on github when you look at the license: https://github.com/aadsm/jschardet/blob/master/LICENSE
@SBoudrias I hate to be a nag but even though you view it as not being a problem, any commercial organization attempting to use open source software will shy away from GPL and derivatives. The FSF licenses are dated and vague.
Believe me, your software's usage will drop over time if you continue to use a piece with an LGPL... even if your own usage of jschardet is not threatened due to your source distribution.
@mrkmg Hey Kevin, any chance you could find an alternative to jschardet?
I know most alternative seems to rely on the ICU binary, so it might be a bit complicated to find a proper alternative.
@SBoudrias but you don't have to find an alternative to jschardet, since you use the external-editor package which uses jschardet.
So the solution would be to find an alternative to external-editor, plus, all dependencies should be MIT.
I would love find an alternative. This has come up before. I will put an effort in today to find an MIT package.
I just launched a new version (2.1.0) which uses https://github.com/runk/node-chardet, licensed under the MIT License.
Also updated tests and verified compatibility from 0.12 to 9.2.0
@mrkmg thanks a ton :)
@SBoudrias So great to hear! Now we need to bump the dependency version (and then I need to get the eslint folks to do it too). :-)
Assembling a PR now.
Edit: Done! #616 . Solely bumps semver for module as well as for dependency.
Most helpful comment
I just launched a new version (2.1.0) which uses https://github.com/runk/node-chardet, licensed under the MIT License.
Also updated tests and verified compatibility from 0.12 to 9.2.0