hunspell | The most popular spellchecking library | Natural Language Processing library

Tried this ?

After some ramblings trying to figure this out got to the root cause.

When using node -r esm index.js, the esm package does already all the work for your (as noted in other answers), and therefore (not mentioned in other answers):

• the package.json should be updated by removing "type:" "module" (as it creates unintended interactions between the native node ES Modules feature and the esm package you installed)

Aside note: if you tried to use node ES Modules and then you try to switch to esm package, it is very easy to miss this point.

You can use -s TOTAL_MEMORY=32MB compiler flag to preset a size at emcc link time. Related question: wasm-ld: error: initial memory too small, 18317952 bytes needed

There is a default limit setting, set to: 16777216 https://github.com/emscripten-core/emscripten/blob/master/src/settings.js#L171

C.Hunspell_create() missing const char* affpath and const char* dpath parameters.

Maybe you also missing some mingw-w64/msys2/cygwin deps packages on Windows. hunspellgo seem not tested on Windows. You needs a linux-like building system (such as mingw-w64/msys2/cygwin) to compile hunspell on Windows. See at https://github.com/hunspell/hunspell#compiling-on-windows . Golang with cgo support on Windows also need some gcc/g++ deps.

As @leandrojmp mentioned in the comment, you need to provide much more information for us to provide a specific recommendation, but for the general tip on improving the reindex(one-time) https://opster.com/blogs/improve-elasticsearch-reindex-performance/ and for ongoing indexing performance follow https://opster.com/blogs/improve-elasticsearch-indexing-rate/ .

Also, you can run the free checkup tool that provides certain optimization which you can do in your cluster.

This will identify and replace incorrectly spelt words with the correct spelling. Note that it will ignore abbreviations as desired, and it assumes all words are separated by a space.

How do I get my packages.config folder back where it was?

If you do not absolutely need packages.config, then do not go back. The PackageReference format offers lots of benefits that you do not want to miss in the long run, your link does not lie. It even solves your next problem.

How do I Uninstall the packages I did not install?

You simply don't, because it will break your library. A NuGet package represents a module or set of features consisting of artifacts like assemblies, content files or build scripts. Such a module may have dependencies that it requires to work, for example an SQLite library. Instead of creating one giant archive that contains all assemblies and files that are required, packages specify dependencies to other packages. This way, you can flexibly consolidate and update packages, especially if there are common dependencies of multiple packages, which also prevents having multiple copies of the same assemblies or files in different versions, which can become problematic.

Let's look at the dependencies of the packages that you are using.

• System.Data.SQLite.Core
  • No dependencies
• WeCantSpell.Hunspell
  • System.Memory for .NET Framework >= 4.5

[...] the only package installed was System Data SQLite Core

This package does not have any dependencies, that is why there were not additional packages.

[...] I only installed System Data SQLite Core and WeCantSpell.Hunspell

If you look at the list above, the Hunspell package requires System.Memory, that explains why it is installed, too. Hunspell will not work without it, it depends on it. I hear you ask, where do the other packages come from then? Each package can have dependencies. Consequently a package can depend on a package that depends on other packages that... I think you get the idea. So let's take another look at dependencies for .NET Framework >= 4.6.1.

• System.Memory
  • System.Buffers
  • System.Numerics.Vectors
  • System.Runtime.CompilerServices.Unsafe

I think that these are all the dependencies that you were looking for. All these packages will be added to your packages.config and this is one good reason to migrate to PackageReference, because it handles transitive package references way better. Suppose you add one package A with a dependency to package B and that has a dependency to package C. Then A has a dependency to C. This is called a transitive dependency.

The older packages.config will add all packages, while PackageReferece will only add A and is smart enough include the other packages, without explicitly adding them. In your example, the project file would only contain the references below.

I believe you want the functions in mozInlineSpellWordUtil.cpp.

From the header:

Assuming that the .bdic are valid then I have established the path of the dictionaries through the environment variable QTWEBENGINE_DICTIONARIES_PATH, for example I have translated the official example into python with the following structure: