-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
@lexical/playground: Moved Vite config to TS and removed code duplication #5744
@lexical/playground: Moved Vite config to TS and removed code duplication #5744
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
06735a7
to
22199de
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.
LGTM, I do think we can have the vite config as .mts (https://vitejs.dev/guide/troubleshooting#config) if we want to move more towards ESM practices.
Bumping the vite to v5 in package.json has been in my do list for a while. In case you want to give it a go. |
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.
@StyleT I think this is good to be merged
replacements: [ | ||
{ | ||
from: /__DEV__/g, | ||
to: 'true', |
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.
should this be false?
This reverted the /esm/ example in the playground from #5618, I'll create another PR to restore it |
Here we extract module resolution config to
viteModuleResolution.ts
and move both Vite configs from.js
to.ts