-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Vite and NPM workspace fixes #5640
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.
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
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #5640 +/- ##
==========================================
- Coverage 55.92% 55.91% -0.02%
==========================================
Files 322 322
Lines 21706 21719 +13
Branches 4427 4431 +4
==========================================
+ Hits 12140 12145 +5
- Misses 8501 8508 +7
- Partials 1065 1066 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* Better error message if a framework isn't detected * Handle NPM workspaces for both Vite and Angular * Error if the node_module binary isn't found * Force vite build to production mode ------ Co-authored-by: Tatsuya Yamamoto <TatsuyaYamamoto@users.noreply.github.com>
* Better error message if a framework isn't detected * Handle NPM workspaces for both Vite and Angular * Error if the node_module binary isn't found * Force vite build to production mode ------ Co-authored-by: Tatsuya Yamamoto <TatsuyaYamamoto@users.noreply.github.com>
Fail detection for vite if the config can't be loaded (seeing this with SvelteKit mostly)