dict-en-gb has become GPL preventing cspell updates

Info

Kind of Issue

• runtime - command-line tools
• building / compiling
• security
• change in behavior
• crash / error

Which Tool or library

• cspell – the command-line spelling tool
• cspell-tools – used for building dictionary files
• cspell-lib – library that does the actual spell checking.
• cspell-trie – tool for working with trie files.

Which Version

Version: @cspell/dict-en-gb 2.0.1, cspell 5.9.1

Issue with supporting library?

• No
• cspell-glob – library for matching glob patterns
• cspell-io – thin file i/o library
• cspell-trie-lib - trie lib
• cspell-trie2-lib - trie lib alternate format

OS:

• Macos
• Linux
• Windows
• Other

version:

N/A

Bug Description

Describe the bug

@cspell/dict-en-gb has become GPL and is not a modular part of cspell. Therefore if an organization cannot use GPL libraries, this effectively makes all of cspell impossible to use as one dictionary has a less permissive license.

I understand that the cspell-dicts is a separate repo, but the change there directly affects the legality of using cspell as a whole since it is not modular.

To Reproduce

1. Organization prohibits GPL licenses
2. Cannot install cspell as it is missing a required dependency @cspell/dict-en-gb

Expected behavior

I see a few possibilities to fix this:

• Find another dictionary for en_GB which is MIT licensed so all of cspell can stay MIT
• Make cspell dictionaries optional peer dependencies so an end user can choose to install only the dictionaries that they want/need. This will make it more cumbersome to use but will give a way to avoid certain dictionaries that have less permissive licenses.

Screenshots

N/A

Additional context

This was introduced via this commit in an effort to change the underlying dictionary dependency

cspell.json

N/A

Example Repository (Optional)

N/A

[Jason3S]

Would you please try cspell@5.10.0-alpha.6

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.