Paket
Nest
Our great sponsors
Paket | Nest | |
---|---|---|
9 | 312 | |
1,988 | 64,263 | |
0.4% | 1.8% | |
8.0 | 9.9 | |
29 days ago | 2 days ago | |
F# | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Paket
-
The Case for C# and .NET
I'm not sure if it will help in your scenario, but faced with a similar problem (~80 project solution, mixed c#/f#, with varying dependencies), I found success with Paket (https://github.com/fsprojects/Paket)
It is much more prevalent in the f# community (at this point `dotnet restore` is a perfectly fine default until you hit trouble), but isn't limited to just being applied there.
-
Introduction to Paket for F#
You can find the official docs here: https://fsprojects.github.io/Paket/
-
The located assembly's manifest definition does not match the assembly reference - The bane of my existence
Another thing that might be worth considering for you is Paket. This is an alternative to using nuget, directly, and will take a little bit of setting up (follow their instructions), but once you have it, it will make sure that all dependencies and transitive dependencies for all your projects are the same. Not 100% sure if this would solve the issue for you, and it might be tricky if the realApplication has unknown shared dependencies with the other projects, but you can give it a try.
-
Scala at Scale at Databricks
Check out https://fsprojects.github.io/Paket/ and https://fake.build/ and https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/get-started-vscode for playing with F#.
-
WebSharper: Getting Started Easily
So I am stuck again when I want to create a web app. Don't laugh. Once again, I come from *NIX environment and the way everything is started in WebSharper is quite confusing at first. I tried to go installation documentation but I don't use Visual Studio nor MonoDevelop. Using paket also doesn't solve my problem since they also seem to use Visual Studio or MonoDevelop.
-
Can't get paket to work for the simplest case
a bit of follow up: this is because the init command you ran defaulted to those frameworks. it could be smarter, or it could default to something more recent. I opened this PR to update this default.
-
What do you think ASP.NET Core is missing or could do better?
If this would be true, there would be no reason for something like Paket to exist.
-
A Brief F# Exploration
I agree with the author about the slow inner loop experience. Recompiling the whole app to see browser changes gets tiring. The .NET team is planning a series of updates to address this in .NET 6. https://github.com/dotnet/core/issues/5510
I also dislike the default workflow for dealing with Nuget forks. I switched to Paket for dependency management which makes this much simpler. https://fsprojects.github.io/Paket/
-
Is it possible to use Paket, with dotnetcore, with packages from github?
Also, I stumbled on this ticket https://github.com/fsprojects/Paket/issues/3064 which seems to confirm my fear that Paket is limited to importing files from Github, not entire packages, but I'm still hoping.
Nest
-
NestJS tip: how to change HTTP server timeouts
When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:
-
Containerize your multi-services app with docker compose
Back: a graphQL server built with Nestjs
-
Full Stack Web Development Concept map
NestJS - opinionated more scalable, but harder to learn docs
-
Don't go all-in Clean Architecture: An alternative for NestJS applications
Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):
- Utilizando Testcontainers para Testes de IntegraĆ§Ć£o com NestJS e Prisma ORM
-
A Gentle Introduction to Containerization and Docker
Itās a text document that contains all the commands a user could call to assemble an image. Letās check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.
-
Scalable REST APIs with NestJS: A Testing-Driven Approach
describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });
-
Rust GraphQL APIs for NodeJS Developers: Introduction
In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:
-
A Step-by-Step Guide to Implement JWT Authentication in NestJS usingĀ Passport
The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.
-
From Frontend to Backend
That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/
What are some alternatives?
NuGet - NuGet Gallery is a package repository that powers https://www.nuget.org. Use this repo for reporting NuGet.org issues.
SailsJS - Realtime MVC Framework for Node.js
BaGet - A lightweight NuGet and symbol server
Koa - Expressive middleware for node.js using ES2017 async functions
Sleet - A static nuget feed generator for Azure Storage, AWS S3, and more.
loopback-next - LoopBack makes it easy to build modern API applications that require complex integrations.
Dotnet CLI - The .NET Core command-line (CLI) tools, used for building .NET Core apps and libraries through your development flow (compiling, NuGet package management, running, testing, ...).
feathers - The API and real-time application framework
fbrary - Create, manage and edit your audio book library from the command line.
Ts.ED - :triangular_ruler: Ts.ED is a Node.js and TypeScript framework on top of Express to write your application with TypeScript (or ES6). It provides a lot of decorators and guideline to make your code more readable and less error-prone. āļø Star to support our work!
fslang-suggestions - The place to make suggestions, discuss and vote on F# language and core library features
Moleculer - :rocket: Progressive microservices framework for Node.js