search

krompaco / hotwired-aspnet

A Blazor SSR sample site with CLI setup for Tailwind CSS and Webpack for Hotwire with Turbo and Stimulus
33 stars 1 forks source link

Publish package to NuGet #1

Open MichalSznajder opened 1 year ago

MichalSznajder commented 1 year ago

It would be awesome to have this on NuGet.

Based on https://github.com/hotwired/turbo-rails I suggest to name it Turbo.AspnetCore. hotwired is both turbo and stimulus.js. AspNet suggests that it also works on .NET 4.7.x/

I think minimal steps are:

krompaco commented 1 year ago

Thanks!

I was thinking that maybe there is some support that could be worked in for help with Stimulus data-attributes and then keep it bundled since it's already quite small. Probably Hotwired is the better name then but you are right that AspNetCore should be in the name.

But maybe it's better to split Stimulus and Turbo like they do on npm and maybe also keep Hotwired since Turbo could be too generic on its own.

"@hotwired/stimulus": "^3.1.0",
"@hotwired/stimulus-webpack-helpers": "^1.0.1",
"@hotwired/turbo": "^7.2.4",

Also maybe there should be something describing me or another name in there so it's not interpreted as an official package?

Ideas...

Maybe these are more in line with MS naming:

MichalSznajder commented 1 year ago

Looking at https://github.com/hotwired/turbo-rails I don't see any stimulus integration.

Krompaco.AspNetCore.Hotwired.Turbo is fine for me. Krompaco.AspNetCore.Hotwired.Stimulus would be good name for stimulus integration. I just wonder if Hotwired is ok or rather it should be Hotwire? Official docs say Hotwire (HTML-over-the-wire), hotwired was used in the past IFAIK.