Search
Items tagged with: nodeJS
JSDB 5.1.0 published¹ 🎉
• Forgetting to pass a custom class that’s persisted in your database in your `JSDB.open()` call now throws instead of corrupting your database by falling back to using an untyped object.
• Added JSDF ver. 2 to 3 database migration script (i.e., JSDB version 2-4 to 5)²
To install update:
npm install @small-tech/jsdb@5.1.0
¹ https://codeberg.org/small-tech/jsdb/releases
² https://codeberg.org/small-tech/jsdb#version-2-to-3
#JavaScriptDatabase #JavaScript #database JSDB #JSDB5 #NodeJS #SmallTech #SmallWeb #web #dev
jsdb
A zero-dependency, transparent, in-memory, streaming write-on-update JavaScript database for the Small Web that persists to a JavaScript transaction log.Codeberg.org
JSDB 5.0.1 published 🎉
• Fixes #14: Crash if DataProxy getHandler() called on object with null prototype. (https://codeberg.org/small-tech/jsdb/issues/14)
To install update:
npm install @small-tech/jsdb@5.0.1
Learn more about JSDB:
https://codeberg.org/small-tech/jsdb#javascript-database-jsdb
#JavaScriptDatabase #JavaScript #database JSDB #JSDB5 #NodeJS #SmallTech #SmallWeb #web #dev
jsdb
A zero-dependency, transparent, in-memory, streaming write-on-update JavaScript database for the Small Web that persists to a JavaScript transaction log.Codeberg.org
To really drive home the above 👆 point that 100% test coverage does not mean ‘bug free’, just found a bug in JSDB¹ 5.0.0 where running JSON.stringify() on a complex custom object (actually: the automatic Proxy of the custom object created by JSDB) results in an error.
Already have a failing test and about to implement fix.
(It’s at this point where the test harness is invaluable.)
¹ https://codeberg.org/small-tech/jsdb
#JavaScriptDatabase #JavaScript #database #JSDB #JSDB5 #NodeJS #SmallWeb #SmallTech
jsdb
A zero-dependency, transparent, in-memory, streaming write-on-update JavaScript database for the Small Web that persists to a JavaScript transaction log.Codeberg.org
JSDB 5.0.0 published 🎉
• Custom classes must have a `constructor` that accepts a parameter object as its only argument. Constructors are run during deserialisation.
• Custom classes can now safely extend other classes (e.g., `EventEmitter`).
• Properties that begin with an underscore (`_`) are treated as private and ignored.
• Objects with null prototypes are supported. i.e., objects created with `Object.create(null, …)`.
Full details: https://codeberg.org/small-tech/jsdb#migrating-from-earlier-versions-of-jsdf
jsdb
A zero-dependency, transparent, in-memory, streaming write-on-update JavaScript database for the Small Web that persists to a JavaScript transaction log.Codeberg.org
Realised last night that JavaScript Database (JSDB) doesn’t run the constructor on persisted custom objects (https://codeberg.org/small-tech/jsdb#custom-data-types) when deserialising them because I didn’t know that you apparently have to define your constructor manually when using Object.create().
Will fix it today but it’s something to watch out for if you’re using Object.create() directly.
For more info, see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/create
#JSDB #customObjects #constructor #bug #JavaScript #NodeJS #SmallTech #SmallWeb
jsdb
A zero-dependency, transparent, in-memory, streaming write-on-update JavaScript database for the Small Web that persists to a JavaScript transaction log.Codeberg.org
Time for a #jobSearch post!
I'm looking for a #typeScript / #python / #RustLang 100% #remote #softwareDev position, both contract and permanent, GMT+2 timezone.
I previously worked as a Senior / Lead / Principal #fullStack developer with #cyberSecurity , #softwareArchitecture and #devOps experience.
I specialize in #react , #nodejs , #django , #fastAPI , #pandas , #postgresql , #docker , #kubernetes , #AWS and #digitalOcean .
Just improved the display of error messages in Kitten¹.
They should be far more robust now.
Run `kitten update` to get the latest.
💕
¹ https://codeberg.org/kitten/app
#Kitten #errorMessages #stackTrace #web #dev #JavaScript #nodeJS
![Screenshot of error message in browser: There’s a cute illustration of a kitten playing with a ball of purple yarn.
The error code (in pink) is 500. The error message reads ‘ReferenceError: meow is not defined’
Under that is a Stack trace split into two sections, ‘From your app’ and ‘From Kitten’.
In the first section, there’s a coed snippet shown with syntax highlighting, line numbers, and striped lines (white/pink):
export default () => kitten.html`
${meow}!
`
The ‘m’ in meow has a pink arrow head (caret) pointing to it.
The stack trace message reads:
While running PageRoute.default [as _handler]
in /index.page.js (line 2, column 5)
In the From Kitten section the following stack messages are visible:
While running PageRoute.lazilyLoadedHandler
in /kitten-bundle.js (line 239183, column 31)
While running loop
in /kitten-bundle.js (line 203214, column 65)
While running next
in /kitten-bundle.js (line 203215, column 73)
While running Array.<anonymous>
in /kitten-bundle.js (line 239777, column 9)](https://friendica.hellquist.eu/photo/preview/640/2431929 "Screenshot of error message in browser: There’s a cute illustration of a kitten playing with a ball of purple yarn.
The error code (in pink) is 500. The error message reads ‘ReferenceError: meow is not defined’
Under that is a Stack trace split into two sections, ‘From your app’ and ‘From Kitten’.
In the first section, there’s a coed snippet shown with syntax highlighting, line numbers, and striped lines (white/pink):
export default () => kitten.html`
${meow}!
`
The ‘m’ in meow has a pink arrow head (caret) pointing to it.
The stack trace message reads:
While running PageRoute.default [as _handler]
in /index.page.js (line 2, column 5)
In the From Kitten section the following stack messages are visible:
While running PageRoute.lazilyLoadedHandler
in /kitten-bundle.js (line 239183, column 31)
While running loop
in /kitten-bundle.js (line 203214, column 65)
While running next
in /kitten-bundle.js (line 203215, column 73)
While running Array.<anonymous>
in /kitten-bundle.js (line 239777, column 9)")
