Web Worker / Node Typing & a few project tweaks

[RaenonX]

Thanks for the project!

This includes the following changes:

• Some project files update, including /dist removal, Makefile args updates
• GLPK version bumped to v5
• Split exports / typings for Web Worker / Node version
  • Since Web Worker mostly returns Promise<> due to the nature of web workers while Node returns synchronously, I split the typing to GLPKWebWorker and GLPKNode.
  • This should help addressing Types do not include Promise<> #43.
• Added terminate() for both version to help memory management. This should help addressing Managing memory for multiple LP instances #45
• Added Github Actions workflow for automated version publishing

Since I am having a rather faster pace on my main project depending on this. I have included these commits, made them to be v5, and published on https://www.npmjs.com/package/@raenonx/glpk.js.

[jvail]

Salut @RaenonX, thank you for sharing. I am a bit less fast paced it seems ... good that you have solved your problem with your own package: Keep the PR open please I will need a bit of time to look into it and it is certainly a good idea to renovate the whole lib.
However, I am surprised that you have not switched to another LP solution in wasm. I am sure there are new/better ways to do that nowadays since the C lib of GLPK hasn't been updated since 2000. Out of curiosity: Why are you still using this library?

[RaenonX]

Salut @RaenonX, thank you for sharing. I am a bit less fast paced it seems ... good that you have solved your problem with your own package: Keep the PR open please I will need a bit of time to look into it and it is certainly a good idea to renovate the whole lib.
However, I am surprised that you have not switched to another LP solution in wasm. I am sure there are new/better ways to do that nowadays since the C lib of GLPK hasn't been updated since 2000. Out of curiosity: Why are you still using this library?

No problem, I can keep the PR open!

tbh I forgot the exact reason why I picked this package over other packages initially, but I didn't switch because I find it too much to switch given that I broke the implementation regarding GLPK in my code to many pieces.
My gut feeling was (fixing this package + experience building and publishing package) is better than (trying other packages + loss of the experience building packages + the risk of the same OOM issue) so I ended up stayed using this package