Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

General dotnet tooling realignment 2023? #61

Open
jkone27 opened this issue May 21, 2023 · 1 comment
Open

General dotnet tooling realignment 2023? #61

jkone27 opened this issue May 21, 2023 · 1 comment

Comments

@jkone27
Copy link

jkone27 commented May 21, 2023 •
edited
Loading

Upgrade to dotnet tool manifest for fake (and paket, if paket is needed), NET6+ (or NET8), Fake, Vite, ditch octokit and nuget for dotnet publish?

I tried to test build another branch now but doesn't seem possible atm, it seems this repo needs a general upgrade in tooling, maybe webpack could be ditched in favour of vite or perla (simpler to setup?) @AngelMunoz

https://github.com/AngelMunoz/Perla.
@jkone27 jkone27 changed the title Upgrade to dotnet tool manifest for fake (and paket, if paket is needed), NET6+ (or NET8), Fake, Vite Upgrade to dotnet tool manifest for fake (and paket, if paket is needed), NET6+ (or NET8), Fake, Vite, ditch octokit and nuget for dotnet publish? May 21, 2023
@jkone27 jkone27 changed the title Upgrade to dotnet tool manifest for fake (and paket, if paket is needed), NET6+ (or NET8), Fake, Vite, ditch octokit and nuget for dotnet publish? General dotnet tooling realignment 2023? May 21, 2023
@AngelMunoz
Copy link

No promises, I might give this one a look over the weekend either vite or perla should be good (it can be a good project to test perla also as well)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AngelMunoz @jkone27