home.social

#lerna — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #lerna, aggregated by home.social.

  1. Почему мы выбрали gRPC вместо tRPC?

    🛠️ Почему мы выбрали gRPC вместо tRPC При разработке крупных приложений на основе Domain Driven Design переход от монолита к микросервисам требует сохранения принципов ООП для поддержки кода. gRPC предоставляет ряд преимуществ перед tRPC: возможность использования Golang для высоконагруженных компонентов, отказ от паттерна роутера в пользу прямых вызовов микросервисов, эффективную статическую типизацию через интерфейсы, децентрализованную архитектуру с возможностью частичного перезапуска микросервисов и автоматический мап методов классов без boilerplate кода.

    habr.com/ru/articles/858186/

    #grpc #typescript #javascript #yarnworkspaces #microservices #es6 #es6modules #nx #lerna

  2. 5 проблем микросервисов на gRPC + TypeScript

    🔥 Архитектура монорепозитория с микросервисами на gRPC и TypeScript: 1. Работа с gRPC через TypeScript : Генерация типов из proto-файлов с помощью скрипта на JS без бинарников, поддержка IntelliSense и сгенерированного исполняемого кода. 2. Запуск backend без Docker : Использование npm start и PM2 для отладки через chrome://inspect и добавления console.log в бандл после сборки 3. Единая ответственность БД : Луковичная архитектура (Model View Presenter) в общем модуле БД, поддерживающая принцип единой ответственности и исключающая bottleneck, так как дублируется по микросервисам. 4. Методы микросервисов без Postman : Точка входа apps/host-test для запуска кода или разработки тестирования. 5. Автоматическая проверка SOLID : Нейросеть анализирует классы при транспиляции, поддерживая чистоту архитектуры и документируя проект в markdown.

    habr.com/ru/articles/857432/

    #typescript #javascript #es6 #nx #lerna #monorepo #grpc #microservices #protobuf #gpt4all

  3. Пакетируем легко и просто с помощью Lerna

    Всем привет! Меня зовут Иван Кузнецов, я Head of Frontend в Uzum Market. Расскажу о сложностях, с которыми мы столкнулись на пути к реализации микрофронтендовой архитектуры, и поделюсь результатами, которые мы получили в процессе пакетирования наших решений с помощью Lerna. Надеюсь, тебе, дорогой читатель, будет очень интересно :)

    habr.com/ru/companies/uzum/art

    #lerna #Nexus #NX #npm #npmпакет #uzum #uzumtech

  4. SimpleWebAuthn v8.0.0 has been released! The highlight of this release: first-class Deno support, as well as unofficial support for CloudFlare Workers and Bun! Basically anything that can run JavaScript or TypeScript on the back end should now be able to pull in this project, including CommonJS and ECMAScript modules!

    Check out the changelog, there are a couple of minor breaking changes:

    github.com/MasterKale/SimpleWe

    And if you have a Deno project you've been wanting to use SimpleWebAuthn with (without having to resort to npm: specifiers) you can find the project on deno.land here:

    deno.land/x/simplewebauthn@v8.

    Time to rest 😮‍💨

    #simplewebauthn #node #nodejs #deno #bun #cloudflare #typescript #javascript #webauthn #passkeys #pnpm #lerna

  5. Does anybody have any suggestions about how to make a #monorepo perform well given what I have said? Any good tools to use or should I just not do it? #Lerna #NX #Turborepo etc.? Stack currently Jekyll, but will be moving to something Node/Deno flavoured.

  6. Does anybody have any suggestions about how to make a #monorepo perform well given what I have said? Any good tools to use or should I just not do it? #Lerna #NX #Turborepo etc.? Stack currently Jekyll, but will be moving to something Node/Deno flavoured.

  7. Does anybody have any suggestions about how to make a #monorepo perform well given what I have said? Any good tools to use or should I just not do it? #Lerna #NX #Turborepo etc.? Stack currently Jekyll, but will be moving to something Node/Deno flavoured.

  8. Does anybody have any suggestions about how to make a #monorepo perform well given what I have said? Any good tools to use or should I just not do it? #Lerna #NX #Turborepo etc.? Stack currently Jekyll, but will be moving to something Node/Deno flavoured.

  9. @mattofthefuture Personally I really really like using npm workspaces and wireit. Does everything I need an nothing I don't. I used to use #lerna whenever I needed something like this. (which is now run by nx) in short workspaces handles running commands and linking and #wireit let's you create performance dependant builds. Example: github.com/joist-framework/joi

  10. My "Best Practices" for professional full-featured #Node / #TypeScript mono repositories. I came up with this:

    github.com/bhouston/esbuild-ts

    Any feedback for further improvements?

    #lerna #esbuild #koa

  11. 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.

  12. 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.

  13. 🐉 Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.

    github.com/lerna/lerna

    #lerna #JavaScript #libraries #monorepo

  14. What tool do you use to manage your ? Please comment which feature you like the most or if you use another tool.

  15. I've had a long day of #git intricacies, #npm trivialities, and re-learning #lerna. I'm finally confident enough at the command line for this. Next, start publishing Release Candidate modules for an internal framework tomorrow. This kind of shit makes me a bit nervous until I've done it a few times.