Paket
storybook
Our great sponsors
Paket | storybook | |
---|---|---|
9 | 321 | |
1,988 | 82,727 | |
0.4% | 0.7% | |
8.0 | 10.0 | |
29 days ago | 4 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.
storybook
-
Storybook not picking up tailwindcss
[Bug]: Configuration with TailwindCss Next.js using Tailwind with Storybook
-
Astro.js as an alternative to Next.js: pushing the limits
Astro has no runtime. This means no unit tests. This also means no Storybook for your Astro components (although, they’re working on it!)
-
Release Radar • March 2024 Edition
If you're into UI development, then you need to know about Storybook. It's a frontend workshop for building UI components and pages in isolation. The latest version brings some big improvements for testing and documentation with built-in visual testing. There's also React Server Component support, improved controls for React and Vue projects, as well as improved Vite architecture, Vitest testing, and Vite 5 support. Check out all the major changes in the Storybook changelog.
-
Top 10 Tools Every React Developer Needs in 2024
Storybook
-
Announcing AnalogJS 1.0 🚀
We are continuing to make building fullstack websites and application with Analog and Angular as seamless as possible, and extending the Angular ecosystem through integrations with Astro, Nx, [Vitest]https://analogjs.org/docs/features/testing/vitest, Storybook, and more.
-
Storybook 8
Storybook is the industry standard UI tool for building, testing, and documenting components and pages. It’s used by thousands of teams globally, integrates with all major JavaScript frameworks, and combines with most leading design and developer tools.
-
Add Cypress, Playwright, and Storybook to Nx Expo Apps
Expo has first-class support for building full-stack websites with React, so I can leverage that to add Cypress/Playwright for E2E testing and add the Storybook for UI components.
-
13 best React debugging tools
Storybook emerges as a pioneering solution among React debugging tools, offering an interactive environment for developers to create and test UI components. With its robust platform, teams can build, organize, and design UI components, and even entire screens, without the hurdles of business logic and plumbing.
-
Javascript is hard ayy eff
3) Look into things like StoryBook for your components - https://storybook.js.org/ - they help you get into good practices and expose you to some more advanced techniques but in a gradual and friendly way, and again, it's good to get into good habits from the start, and these help make sure you're getting into those good habits (it can be hard to learn good habits, but being forced into them helps, I find!)
-
Storybook 7.6 is out!
[Storybook 7.6](https://github.com/storybookjs/storybook/releases) is here with increased performance and much more! 🔥 Improved SWC support 🧪 New test utilities and fast build mode 🔼 NextJS SWC + avif support & fixes 🤡 SvelteKit page and navigation mocking ⚛️ React-docgen upgrade 🎨 Controls a11y, background theming, and viewports 🩺 CLI: The doctor is in! 🚫 Addons: Remove React as a peer dependency 🪦 Storyshots and Vue2 deprecated
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.
Docusaurus - Easy to maintain open source documentation websites.
BaGet - A lightweight NuGet and symbol server
fluentui-blazor - Microsoft Fluent UI Blazor components library. For use with .NET 6.0 or higher Blazor applications
Sleet - A static nuget feed generator for Azure Storage, AWS S3, and more.
react-styleguidist - Isolated React component development environment with a living style guide
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, ...).
fractal - A tool to help you build and document website component libraries and design systems.
fbrary - Create, manage and edit your audio book library from the command line.
svelte-luna - svelte ui kit
fslang-suggestions - The place to make suggestions, discuss and vote on F# language and core library features
primeng - The Most Complete Angular UI Component Library