-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
fix(vite): PCV3 Plugin update to use resolveConfig #21287
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 6e0c284. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
941346a
to
1e99127
Compare
1e99127
to
7a448a2
Compare
Victor got this error when running with
We can fix it by passing in the absolute path of the viteConfig. Can we sneak that into this PR please? 🙏 |
7a448a2
to
d785db0
Compare
It's still not working for this repo https://github.com/jaysoo/vite-app-libs I think once the config is resolved we still need to check the inputs to make sure they exist? |
d785db0
to
6d877dd
Compare
There was a problem using Maybe we can look into that further, But moving forward, using |
6d877dd
to
a4ff6ab
Compare
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.
Qwik's config loads as
path: '/Users/jack/projects/qwik-app/vite.config.ts',
config: {
plugins: [ [Array], [Object], [Object] ],
server: { headers: [Object] },
preview: { headers: [Object] }
},
dependencies: [ 'vite.config.ts' ]
}
We should get this to work because unlike Remix, Qwik expects users to run vite build
, etc.
a4ff6ab
to
b7dd016
Compare
b7dd016
to
6e0c284
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
No description provided.