Eli Peters
Eli Peters
Probably need to update the [readme on NPM]( https://www.npmjs.com/package/merge-img) also..
I'm also noticing a third reduction in file size between `img.getMIME()` over implicitly setting the mime type to `Jimp.MIME_JPEG` All source images I used are jpg and the result is...
- [ ] Provide image map for slicing I've[ forked this](https://github.com/elipeters/merge-img) though it's brutal - only useful for horizontal merge.
[All websites were once built this way](https://www.htmlgoodies.com/tutorials/web_graphics/article.php/3906376/Web-Developer-Class-Use-Image-Slicing-to-Load-Web-Images-Quickly.htm)... slice up a large image and place inside tables then http request the heck out of it. ...though now in reverse... output something...
bump - like 2017
`throw new Error("Wrong filter given :" + filter);` **filter** is out of scope and throws undefined
4 mins later I manage to answer my question... the "odd" part was the key. Swapping the two inputs makes more sense. ```javascript User.update({id:req.user.id},params).exec(function(err, res){ //do something }); ``` What...
...also you must return the update for it to execute. ```javascript User.update({id:req.user.id},params); //doesn't update User.update({id:req.user.id},params).exec(function(err,users){ //update as expected }); ```