Activity, over time
Daily observations from the public event archive.
Attention
Daily stars & forks
Star accumulation
Cumulative stars
Pull requests
Daily opens & merges
Conversations
Daily issues & comments
Community
Daily accounts & reviews
Releases
Daily releases
Trending history
Daily top 10 · last 90 days · UTC
Mentions
Stars
Forks
Contributors
Latest stargazers
The last 10 distinct accounts we observed this year.
Most active participants
PR, issue, comment & review events in the past year.
Packages
| Package | Version | Downloads · 30d | Trend · 30d |
|---|---|---|---|
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
| — | — | — | |
@polar-sh/adapter-utilsv1.1.0 | v1.1.0 | ≥67.7K | |
@polar-sh/better-authv2.1.0 | v2.1.0 | ≥72.1K | |
@polar-sh/checkoutv0.4.3 | v0.4.3 | ≥133.7K | |
@polar-sh/nextjsv1.1.0 | v1.1.0 | ≥49.9K | |
@polar-sh/nuxtv1.1.0 | v1.1.0 | ≥1.7K | |
@polar-sh/tanstack-startv1.1.0 | v1.1.0 | ≥980 | |
@polar-sh/uiv0.1.2 | v0.1.2 | ≥36.2K |
README badges
Embed a badge in your README or website.
Live mentions · last 30 days
Mentions
@_maxscn @mazeincoding Maze has a point (as I understand it) - I don't know how opencode repo looks like but I think polar.sh is an example of feature/module based location github.com/polarsource/polar/tree/main/server/pol… /auth /benefits All hold similar things inside (as needed) and if you work on a single feature you indeed modify only what's inside a single feature That's said I find layer based organization easier to reason about: /entrypoints /application /domain /infrastructure Yes, for a single feature, such as auth there will be an auth api route (entrypoint), an application handler and maybe some infra code but I like it this way better