Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / techgems/Vite.NET issues and pull requests
#22 - ESM support for vite-dotnet NPM package due to externalize-deps
Issue -
State: open - Opened by ericgarzagzz 9 months ago
#21 - ProductionViteSpaScripts.cshtml path fixes.
Pull Request -
State: open - Opened by hdimon 11 months ago
- 3 comments
#20 - ViteDotNetPlugin type fix to get rid of typescript error.
Pull Request -
State: closed - Opened by hdimon 11 months ago
#19 - Add scripts to page in development mode only after Vite server is ready.
Pull Request -
State: closed - Opened by hdimon 11 months ago
- 1 comment
#18 - Empty vite output directory on every build.
Pull Request -
State: closed - Opened by hdimon 11 months ago
- 1 comment
#17 - Getting Started : production build seems to be pointing to the wrong url?
Issue -
State: open - Opened by rosdi over 1 year ago
- 1 comment
#16 - Getting Started : Vite Dev Server Not Found
Issue -
State: open - Opened by rosdi over 1 year ago
- 1 comment
#15 - In Vite Plugin, port specified is not being used.
Issue -
State: closed - Opened by techgems over 1 year ago
- 1 comment
#14 - Investigate possibility of backend support for .NET Framework tag helper equivalents
Issue -
State: open - Opened by techgems over 1 year ago
#13 - Add support for Blazor vite script integrations
Issue -
State: open - Opened by techgems over 1 year ago
#12 - Write up a basic dotnet template
Issue -
State: open - Opened by techgems over 1 year ago
#11 - Add an NPM package readme
Issue -
State: open - Opened by techgems over 1 year ago
#10 - Add a "Use cases" page in the documentation providing examples of things you can do with Vite.NET that are harder to do without it.
Issue -
State: closed - Opened by techgems over 1 year ago
- 1 comment
#9 - Improve style of missing app manifest error.
Issue -
State: closed - Opened by techgems over 1 year ago
- 1 comment
#8 - When using multiple SPAs, server crashes if not all production manifest files exist.
Issue -
State: closed - Opened by techgems over 1 year ago
- 1 comment
#7 - Allow Vite plugin to receive an additional optional parameter for remote deployment
Issue -
State: open - Opened by techgems over 1 year ago
#6 - Auto start multiple SPAs based on configuration
Issue -
State: closed - Opened by techgems over 1 year ago
- 1 comment
#5 - Create NPM package for Vite plugin
Issue -
State: closed - Opened by techgems over 1 year ago
- 1 comment
#4 - Create Nuget package for Vite.NET
Issue -
State: closed - Opened by techgems over 1 year ago
- 1 comment
#3 - Write documentation site
Issue -
State: closed - Opened by techgems over 1 year ago
#2 - Production bundled assets do not reflect their provided folder.
Issue -
State: closed - Opened by techgems over 1 year ago
- 1 comment
#1 - Assets in public folder do not show up when using <dev-vite-scripts /> tag helper
Issue -
State: closed - Opened by techgems over 1 year ago
- 1 comment