My "Best Practices" for professional full-featured #Node / #TypeScript mono repositories. I came up with this:
https://github.com/bhouston/esbuild-ts-monorepo
Any feedback for further improvements?
#node #typescript #lerna #esbuild #koa
People who are working with #npm #monorepo's, if I have a package (eslint config) in the monorepo that is used as `devDependency` in other package from the same repo, and that other package is going to be published. Does this `devDependency` has to be published too? Or can it stay private? I really don't see sense publishing it, but also couldn't find information whether npm cares about devDeps...
Also tagging #nx #lerna #turborepo #pnpm #javascript, in case you guys maybe know the answer.
#nx #JavaScript #pnpm #turborepo #lerna #monorepo #npm
Whatβs new with Lerna 6.5?
https://blog.nrwl.io/whats-new-with-lerna-6-5-4a4f69371504
#ES_Next_News #ECMAScript #JavaScript #Lerna
#es_next_news #ecmascript #javascript #lerna
I hate "starting over" but I don't have a choice. Not a full starting over of my code, but the repo it is in.
I have a #lerna 5 #monorepo but in upgrading minor versions, I hit an incompatibility with the older react-scripts 4.x and react 17. My libs and storybooks run, but CRA apps won't anymore.
So I gotta start over with staging a new repo. Should I stick with lerna 6 or is it worth incorporating #NX along the way?
code is client JS, MUI 5 components, and lots of custom hooks.
π Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
#lerna #javascript #libraries #MonoRepo
Lerna Reborn [25-min. video]
https://www.youtube.com/watch?v=CNdDv2MsBuw
#EsNextNews #EcmaScript #JavaScript #Lerna #MonoRepo
#EsNextNews #ecmascript #javascript #lerna #monorepo
What tool do you use to manage your #monorepo? Please comment which feature you like the most or if you use another tool. #turborepo #lerna #pnpm #yarn
#monorepo #turborepo #lerna #pnpm #yarn
RT @shirenbeat@twitter.com
λ‘컬 μ½λ© νλ μ΄κ·ΈλΌμ΄λ λ§λ€κΈ° ννΈ ν¬
https://blog.shiren.dev/2021-02-22/
#frontend #nodejs #tdd #lerna
π¦π: https://twitter.com/shirenbeat/status/1363652016958939137
RT @shirenbeat@twitter.com
μμ£Ό μ°λ νκ²½μ 미리 λ§λ€μ΄ λκ³ μ¦μμμ κΊΌλ΄ μΈ μ μλ μ½λ© νλ μ΄κ·ΈλΌμ΄λλ₯Ό λ§λ€λ©΄μ μμ¦ FE κ°λ° νκ²½μ μκ°νλ κΈμ
λλ€. κ° λꡬμ λν μ 짧μ μκ°λ μ μ΄λ΄€μ΄μ. :) https://blog.shiren.dev/2021-02-15/
#frontend #nodejs #tdd #lerna
π¦π: https://twitter.com/shirenbeat/status/1361172727248261122
Is there any example of "#OpenSource complicity" with bad actors as currently defined, that *doesn't* involve permissive/non-reciprocal licensing? So far, all the examples I've heard of involve profiting from proprietary stuff derived from #FLOSS.
#OpenSource #FLOSS #lerna #FreeSoftware #FOSS