Gathering detailed insights and metrics for lazy-ass
Gathering detailed insights and metrics for lazy-ass
Gathering detailed insights and metrics for lazy-ass
Gathering detailed insights and metrics for lazy-ass
lazy-ass-helpful
lazy-ass plugin to automatically show helpful info for failed assertions
define-lazy-prop
Define a lazily evaluated property on an object
available-versions
Returns a promise with new versions higher than given for a npm module
lazy-cache
Cache requires to be lazy-loaded when needed.
npm install lazy-ass
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
69 Stars
125 Commits
5 Forks
3 Watching
2 Branches
1 Contributors
Updated on 21 Oct 2024
Minified
Minified + Gzipped
TypeScript (76.15%)
JavaScript (12.29%)
HTML (11.57%)
Cumulative downloads
Total Downloads
Last day
-2.6%
1,116,618
Compared to previous day
Last week
4.3%
5,881,418
Compared to previous week
Last month
9.2%
24,495,915
Compared to previous month
Last year
7.4%
274,479,600
Compared to previous year
Lazy assertions without performance penalty
Note: only tested against Node 4+
Regular assertions evaluate all arguments and concatenate message EVERY time, even if the condition is true.
1console.assert(typeof foo === 'object', 2 'expected ' + JSON.stringify(foo, null, 2) + ' to be an object');
Lazy assertion function evaluates its arguments and forms a message ONLY IF the condition is false
1const {lazyAss} = require('lazy-ass') 2lazyAss(typeof foo === 'object', 'expected', foo, 'to be an object'); 3// shorter version 4const {lazyAss: la} = require('lazy-ass') 5la(typeof foo === 'object', 'expected', foo, 'to be an object');
Concatenates strings, stringifies objects, calls functions - only if condition is false.
1function environment() {
2 // returns string
3}
4var user = {} // an object
5lazyAsync(condition, 'something went wrong for', user, 'in', environment);
6// throws an error with message equivalent of
7// 'something went wrong for ' + JSON.stringify(user) + ' in ' + environment()
Node: npm install lazy-ass --save
then var la = require('lazy-ass');
.
You can attach the methods to the global object using
require('lazy-ass').globalRegister();
.
Browser: bower install lazy-ass --save
, include index.js
,
attaches functions lazyAss
and la
to window
object.
You can pass as many arguments to lazyAss after the condition. The condition will be evaluated every time (this is required for any assertion). The rest of arguments will be concatenated according to rules
There will be single space between the individual parts.
Sometimes you do not want to throw an error synchronously, breaking the entire
execution stack. Instead you can throw an error asynchronously using lazyAssync
,
which internally implements logic like this:
1if (!condition) { 2 setTimeout(function () { 3 throw new Error('Conditions is false!'); 4 }, 0); 5}
This allows the execution to continue, while your global error handler (like my favorite Sentry) can still forward the error with all specified information to your server.
1lazyAss.async(false, 'foo'); 2console.log('after assync'); 3// output 4after assync 5Uncaught Error: foo
In this case, there is no meaningful error stack, so use good message arguments - there is no performance penalty!
If the condition itself is an instance of Error, it is simply rethrown (synchronously or asynchronously).
1lazyAss(new Error('foo'));
2// Uncaught Error: foo
Useful to make sure errors in the promise chains are not silently ignored.
For example, a rejected promise below this will be ignored.
1var p = new Promise(function (resolve, reject) { 2 reject(new Error('foo')); 3}); 4p.then(...);
We can catch it and rethrow it synchronously, but it will be ignored too (same way, only one step further)
1var p = new Promise(function (resolve, reject) { 2 reject(new Error('foo')); 3}); 4p.then(..., lazyAss);
But we can actually trigger global error if we rethrow the error asynchronously
1var p = new Promise(function (resolve, reject) { 2 reject(new Error('foo')); 3}); 4p.then(..., lazyAssync); 5// Uncaught Error: foo
Typically, JavaScript evaluates the condition expression first, then calls lazyAss. This means the function itself sees only the true / false result, and not the expression itself. This makes makes the error messages cryptic
lazyAss(2 + 2 === 5);
// Error
We usually get around this by giving at least one additional message argument to explain the condition tested
lazyAss(2 + 2 === 5, 'addition')
// Error: addition
lazyAss has a better solution: if you give a function that evaluates the condition expression, if the function returns false, the error message will include the source of the function, making the extra arguments unnecessary
lazyAss(function () { return 2 + 2 === 5; });
// Error: function () { return 2 + 2 === 5; }
The condition function has access to any variables in the scope, making it extremely powerful
var foo = 2, bar = 2;
lazyAss(function () { return foo + bar === 5; });
// Error: function () { return foo + bar === 5; }
In practical terms, I recommend using separate predicates function and passing relevant values to the lazyAss function. Remember, there is no performance penalty!
var foo = 2, bar = 2;
function isValidPair() {
return foo + bar === 5;
}
lazyAss(isValidPair, 'foo', foo, 'bar', bar);
// Error: function isValidPair() {
// return foo + bar === 5;
// } foo 2 bar 2
This library is fully tested under Node and inside browser environment (CasperJs). I described how one can test asynchronous assertion throwing in your own projects using Jasmine in a blog post.
If you use this function from a TypeScript project, we provide ambient type definition file. Because this is CommonJS library, use it like this
1import la = require('lazy-ass') 2// la should have type signature
Author: Gleb Bahmutov © 2014
License: MIT - do anything with the code, but don't blame me if it does not work.
Spread the word: tweet, star on github, etc.
Support: if you find any problems with this module, email / tweet / open issue on Github
Copyright (c) 2014 Gleb Bahmutov
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 0/27 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
43 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More