-
-
Notifications
You must be signed in to change notification settings - Fork 124
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
breaking: no index html #289
Conversation
dai-shi
commented
Dec 18, 2023
•
edited
Loading
edited
- examples
- website
- fixtures
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit f48130f:
|
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.
Waiting for localhost:62143..62143 stderr: WebSocket server error: Port is already in use
62143 stdout: ready: Listening on http://localhost:62143/
62143 stderr: (!) Could not auto-determine entry point from rollupOptions or html files and there are no explicit optimizeDeps.include patterns. Skipping dependency pre-bundling.
.
Connected!
debug: [vite] connecting...
debug: [vite] connected.
info: %cDownload the React DevTools for a better development experience: https://reactjs.org/link/react-devtools font-weight:bold
62143 stdout: 11:01:21 PM [vite] ✨ new dependencies optimized: react-dom
62143 stdout: 11:01:21 PM [vite] ✨ optimized dependencies changed. reloading
info: %cDownload the React DevTools for a better development experience: https://reactjs.org/link/react-devtools font-weight:bold
error: Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
error: Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
error: Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
error: Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
error: The above error occurred in the <Counter> component:
at Counter (http://localhost:62143/@fs/C:/Users/himse/Code/waku/examples/11_form/src/components/Counter.tsx:30:3)
at div
at Slot (http://localhost:62143/@fs/C:/Users/himse/Code/waku/packages/waku/dist/client.js:85:24)
at Root (http://localhost:62143/@fs/C:/Users/himse/Code/waku/packages/waku/dist/client.js:65:24)
Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
x 1 [chromium] › examples-smoke.spec.ts:173:9 › smoke test on 11_form: dev › check title (6.0s)
Waiting for localhost:62163..62163 stderr: WebSocket server error: Port is already in use
This reverts commit de92f69.
// XXX I don't know why/how this works | ||
import '../style.css'; |
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.
This seems to work well for production (= npm run website:prd
),
but it's very flaky in development (npm run website:dev
).
Can anyone help investigating what's the right way in vite?