--- title: I don’t really use libraries anymore | daily.dev description: AI code generation is fundamentally changing how developers approach dependencies and libraries. Instead of installing packages for common tasks, developers... canonical: https://daily.dev/posts/i-don-t-really-use-libraries-anymore-kqbtj9npq twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: I don’t really use libraries anymore | daily.dev og:description: AI code generation is fundamentally changing how developers approach dependencies and libraries. Instead of installing packages for common tasks, developers... og:url: https://daily.dev/posts/i-don-t-really-use-libraries-anymore-kqbtj9npq og:image: https://api.daily.dev/og/posts/kqbTJ9NPQ.png og:image:alt: I don’t really use libraries anymore og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # I don’t really use libraries anymore **[Theo - t3․gg](https://daily.dev/sources/t3dotgg)** · 32 min read · 48 upvotes · 18 comments ## Summary AI code generation is fundamentally changing how developers approach dependencies and libraries. Instead of installing packages for common tasks, developers are increasingly using AI to generate custom implementations directly in their codebase. This shift eliminates supply chain risks, reduces dependency bloat, and gives teams full control over their code. Examples include replacing libraries like Tkumi and fast-float with AI-generated alternatives that are simpler to maintain and better integrated. The trend suggests prompts may become the new libraries, with developers sharing prompts instead of packages. This has implications for open source sustainability, as well-documented popular libraries become easier to replace with AI-generated code. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@rubenalopes** · 21 upvotes > This can only be rage bait **@cptmaumau** · 15 upvotes > Pure content bait, no way anyone does that. **@eric6** · 10 upvotes > You can try to reinvent everything yourself, but it is neither wise nor beneficial in terms of productivity, token cost, and project stability. **@xghozt** · 5 upvotes > Imagine being proud of reinventing the wheel. **@rafalnawojczyk** · 4 upvotes > So many comments about reinventing the wheel. I would say it's only partially true. > > I've seen sooo many codebases, where they had literally libraries for one specific functions. The perfect example is the `validate-npm-package-name` which was used WIDELY by most of the libs like React/Next and couple of more. > It's a one file lib, that only validates the npm package name that you assign during the `create react app` call. ## Similar posts on daily.dev - [AI Has Taken Over Open Source](https://daily.dev/posts/ai-has-taken-over-open-source-lgnwefiwc) · Socket · 0 upvotes · 0 comments - [Don't fall into the anti-AI hype](https://daily.dev/posts/don-t-fall-into-the-anti-ai-hype-kp54wqj8l) · Hacker News · 4 upvotes · 0 comments - [Do Component Libraries Still Matter in the Age of AI?](https://daily.dev/posts/do-component-libraries-still-matter-in-the-age-of-ai--cgio1zsn1) · Telerik · 9 upvotes · 3 comments --- Tags: [#ai](https://daily.dev/tags/ai), [#javascript](https://daily.dev/tags/javascript), [#react](https://daily.dev/tags/react), [#npm](https://daily.dev/tags/npm) [View this post on daily.dev](https://daily.dev/posts/i-don-t-really-use-libraries-anymore-kqbtj9npq) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"I don’t really use libraries anymore","url":"https://daily.dev/posts/i-don-t-really-use-libraries-anymore-kqbtj9npq","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/i-don-t-really-use-libraries-anymore-kqbtj9npq"},"datePublished":"2026-01-23T12:58:04.972Z","dateModified":"2026-01-23T13:03:39.835Z","description":"AI code generation is fundamentally changing how developers approach dependencies and libraries. Instead of installing packages for common tasks, developers...","image":"https://i.ytimg.com/vi/u9P3CKwtRnM/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/u9P3CKwtRnM/sddefault.jpg","isAccessibleForFree":true,"articleSection":"Theo - t3․gg","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Theo - t3․gg","logo":"https://media.daily.dev/image/upload/s--UmX7IyU3--/f_auto/v1704628081/logos/t3dotgg.jpg","url":"https://daily.dev/sources/t3dotgg"},"commentCount":18,"discussionUrl":"https://daily.dev/posts/i-don-t-really-use-libraries-anymore-kqbtj9npq","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":48},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":18}],"keywords":"ai,javascript,react,npm","timeRequired":"PT32M","video":{"@type":"VideoObject","name":"I don’t really use libraries anymore","description":"AI code generation is fundamentally changing how developers approach dependencies and libraries. Instead of installing packages for common tasks, developers...","thumbnailUrl":"https://i.ytimg.com/vi/u9P3CKwtRnM/sddefault.jpg","uploadDate":"2026-01-23T12:58:04.972Z","duration":"PT32M","url":"https://api.daily.dev/r/kqbTJ9NPQ","embedUrl":"https://www.youtube.com/embed/u9P3CKwtRnM"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Theo - t3․gg","item":"https://daily.dev/sources/t3dotgg"},{"@type":"ListItem","position":3,"name":"I don’t really use libraries anymore"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/i-don-t-really-use-libraries-anymore-kqbtj9npq","comment":[{"@type":"Comment","text":"This can only be rage bait","datePublished":"2026-01-25T00:35:46.355Z","url":"https://daily.dev/posts/kqbTJ9NPQ#c-vhWQHgceF","author":{"@type":"Person","name":"Ruben A. Lopes","url":"https://daily.dev/rubenalopes","image":"https://avatars.githubusercontent.com/u/91846217?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":21}},{"@type":"Comment","text":"Pure content bait, no way anyone does that.","datePublished":"2026-01-27T01:19:47.314Z","url":"https://daily.dev/posts/kqbTJ9NPQ#c-yJbiwL4WS","author":{"@type":"Person","name":"Etienne Maurin","url":"https://daily.dev/cptmaumau","image":"https://avatars.githubusercontent.com/u/5366008?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":15}},{"@type":"Comment","text":"You can try to reinvent everything yourself, but it is neither wise nor beneficial in terms of productivity, token cost, and project stability.","datePublished":"2026-01-29T04:05:50.061Z","url":"https://daily.dev/posts/kqbTJ9NPQ#c-5SpcLZpMs","author":{"@type":"Person","name":"Eric","url":"https://daily.dev/eric6","image":"https://lh3.googleusercontent.com/a/ACg8ocKDsRT0VpAlKy7zSlcTVRodj8IYyIrwMOP-NaeUudhB_kRZOc4=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":10}},{"@type":"Comment","text":"Imagine being proud of reinventing the wheel.","datePublished":"2026-01-29T08:41:46.246Z","url":"https://daily.dev/posts/kqbTJ9NPQ#c-tQUPjtEZD","author":{"@type":"Person","name":"XGhozt","url":"https://daily.dev/xghozt","image":"https://avatars.githubusercontent.com/u/5670495?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5}},{"@type":"Comment","text":"So many comments about reinventing the wheel. I would say it’s only partially true.\nI’ve seen sooo many codebases, where they had literally libraries for one specific functions. The perfect example is the validate-npm-package-name which was used WIDELY by most of the libs like React/Next and couple of more.\nIt’s a one file lib, that only validates the npm package name that you assign during the create react app call.","datePublished":"2026-01-29T09:04:38.836Z","url":"https://daily.dev/posts/kqbTJ9NPQ#c-o9gW6Eve0","author":{"@type":"Person","name":"Rafal Nawojczyk","url":"https://daily.dev/rafalnawojczyk","image":"https://avatars.githubusercontent.com/u/102222064?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":4}}]} ```