luis.erlacher/Archon
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
main
Archon/node_modules/.pnpm/boolbase@1.0.0/node_modules/boolbase
History
Luis Erlacher 413c6e59a5
Some checks are pending
Build Images / build-server-docker (push) Waiting to run
Details
Build Images / build-mcp-docker (push) Blocked by required conditions
Details
Build Images / build-agents-docker (push) Blocked by required conditions
Details
Build Images / build-frontend-docker (push) Blocked by required conditions
Details
Build Images / build-server-k8s (push) Blocked by required conditions
Details
Build Images / build-mcp-k8s (push) Blocked by required conditions
Details
Build Images / build-agents-k8s (push) Blocked by required conditions
Details
Build Images / build-frontend-k8s (push) Blocked by required conditions
Details
init
2025-11-04 15:31:52 -03:00
..
index.js init 2025-11-04 15:31:52 -03:00
package.json init 2025-11-04 15:31:52 -03:00
README.md init 2025-11-04 15:31:52 -03:00

README.md

#boolbase This very simple module provides two basic functions, one that always returns true (trueFunc) and one that always returns false (falseFunc).

###WTF?

By having only a single instance of these functions around, it's possible to do some nice optimizations. Eg. CSSselect uses these functions to determine whether a selector won't match any elements. If that's the case, the DOM doesn't even have to be touched.

###And why is this a separate module?

I'm trying to modularize CSSselect and most modules depend on these functions. IMHO, having a separate module is the easiest solution to this problem.