1.44.1 (June 14, 2022)

Sean Montgomery

• new feature - node:http and node:https libraries are now supported within Lambas
• new feature - addslashes filter was added to escape bad characters in filenames
• new feature - escape filter was added to preserve escaped characters like newlines \n when wanting to store the data in its raw form
• improvement - support to override the filename for media attachments when the provided URL doesn't have a proper mime type
• improvement - addon management now shows the addon id number, so make it easier to identify addons using the same name
• bug fix - certain inputs would corrupt the query all records statement which would result in needing to start over or rollback using version history
• bug fix - downloading files within the lightbox viewer were running into access denied errors within the Safari browser
• bug fix - when saving data to a json field within a database table, the keys would change if they ended with punctuation characters

see more release notes

Brandon Hassler

This is awesome! I was literally looking into Lambda today to potentially use to generate an AWS signature. Amazon really pushes using their SDK to "do all the heavy lifting" but if I'm not mistaken that's not currently possible with Xano (I know very little about SDK's)

I've noticed they reference Node.js in their documentation such as this snippet they have:[image.png]With this new Lambda update, does that make this process even more straight forward?

Sean Montgomery

 we don't support all libraries yet, but we do have a crypto library which can do that type of signature.