Thread
Stories related to "Javascript Destructing and Untrusted Data" across the full archive.
DRYing up your JavaScript Jasmine tests with the data provider pattern - JP's blog
(blog.jphpsf.com)
A quick tip where I show a technique to eliminate redundancy Jasmine tests.
The ORM we use didn't support transactions so I wrote this! Hope it's useful.
osm-p2p is a decentralized peer-to-peer database for storing and editing OpenStreetMap nodes, ways, and relations. It includes a node.js server that implements the core functionality of the OSM API, or it can be used completely in the browser using IndexedDB for persistent storage.
Scary shit (if you're on Windows, which is already scary in its own right)
Many claim they don't run ads due to security risk. This is one of CompSci's interesting approaches to reducing it. Worth review for weaknesses or experiments on usability.
52% of all JavaScript npm packages could have been hacked via weak credentials
(bleepingcomputer.com)
I am developing a JavaScript widget. As an example, let's say the widget displays a list of posts published by a given customer.
The usual approach is something like this:
<div id="myposts-widget" data-customer-id="42">Loading...</div>
<script src="https://www.myposts.com/widget.js"><...