Definitely want to look into JIMP library mentioned... curiousities on features likely to be missing, but would be nice include...
For jpeg in particular:
* un-rotate image (in other words, clear the rotation and actually match the image without rotation metadata to the image detail), this happens a lot with images taken on phones.
* preserve/copy metadata (such as geolocation, etc) into newly saved images.
For png:
* palette reduction (and quantization) - png gets a lot smaller when you get your colors to a limited palette, which includes alpha channels. quantization will allow this to be reduced on images with more colors, the effects can be good to very bad, but often a huge boost combined for both with png output.
These are all features that are often missing from these types of libraries, and run into dedicated libraries. I've been hoping for a while that the builds for the libraries used with squoosh could be made into individual npm packages using web-assembly for web and node. Which should allow for interop as long as those wasm bundles are gpl, the use of them afaik doesn't require it.
With JWT, you can have an expiration database, something like an in-memory redis instance or memcached can also work... the jti (token identifier) can be added with a timeout of the token's expiration, so that on request, you can check to see if the token was revoked. You also get the added advantage of not having to query user/role tables or systems on requests, or maintain a state server at all. If you have short lived tokens with a refresh cycle you may not need a "logout" at all.
I'm not going through this one... I've done it in the past... the fact is that at least half of the answers are innacurate, misleading or outright wrong.
Not sure on the new syntax... if this isn't adopted by TS, it's unlikely to see the light of day in JS at this point... also, unsure if there's a babel implementation with this syntax either... Decorators have been in development hell since before ES6/ES2015 was finalized.
So, I'm creating a SQL Server versioned project. We have targets using Windows, Linux and are moving to a containerized environment for testing. SQL projects in Visual Studio can only be built in Windows and we've had some troubles with version conflicts (several customers and internal deployments and growing). So moving to a number list of version scripts... we need a way to run it with all of the above environments.
I created the above module to better support those use cases for script deploys. The export scrips (baseline) from the sql project will only really run via sqlcmd, not to mention issues with UTF8/16le, and windows uses -v for variables and linux uses environment variables... this handles all of those use cases.
About a week of very heavy work with thorough test coverage (about 5 files, mostly small/simple utilities are excluded). There's also a set of integration tests that will create a docker container, and populate it with both a local sqlcmd (if available) and the sqlcmd inside the sql server container instance.