Section No. 1
the collection
- LacewingChrysoperla tokeniferareleasediridescent, catches the lightA JWT library that won't let you make the usual JWT mistakes.
- CephaloteCephalotes cryptovoransreleasedFinds the weak crypto in your code and tells you where it is.
- BagwormPsyche portabilisreleasedCarries your dev shell into a container on any runtime.
- BollwormHelicoverpa documentariareleasedTurns an API spec into the Word document someone asked for.
- dung-beetle-templateScarabaeus schematophagustemplateiridescent, catches the lightAphid, plus a generator that writes the client from an OpenAPI, OpenRPC or .proto document.
- PhasmidCarausius canonicusreleasedProvider-aware email canonicalization, so equal mailboxes compare equal.
Section No. 2
food web
Which animal came from which, and which jobs they pass to each other. Solid lines means parent-child projects dashed lines are work handed to a sibling.
- Aphid-template to dung-beetle-template: Aphid, plus a generator
- dung-beetle-template to RoveBeetle: similar, for UTCP
- Aphid-template to Darter: Aphid, in Dart
- Lacewing to Antlion: wraps a Lacewing profile
- Repletes hands retries to Firefly
- Firefly hands caching to Repletes
- mycocepurus-smithii hands retries, single-flight to Firefly
- Aphid-template hands its transport to Firefly
swipe sideways to see the whole web
Section No. 3
opinions
- 01Solve one problem (or type of problem) well.
- 02Keep dependencies to a minimum.
- 03We force you to make safe/opinionated default choices.
- 04Ship software we'd actually want to use ourselves.
- 05AI is fine, so long used reasonably. One human can't know everything.
- 06DECIDE EARLY, DETAILS MATTER NEVER "just do an MVP and make changes later"! (Be it a spec or anything, this is important!)
- 07We are language agnostic in a sense that we use whatever language is best suited for us to solve a problem, we pick up a language to use when ever needed, we don't force a runtime to do something it should not be doing.
- 08We do this for the love of the game and we do not care about "establishing a userbase or community", unless there is a good reason (e.g. getting usability opinions).
- 09We refuse blind compliance (if we adopt an RFC, there is a reason).
- 10We are not anti-agile, we just don't really use it.
- 11Have a little fun along the way.
- 12Our libraries are generally insects.
Section No. 4
elsewhere
It is all public. Issues and pull requests get read, and nothing here is too precious to argue about.
the org on GitHub ↗lacewing on npm ↗lacewing docs ↗