-
Notifications
You must be signed in to change notification settings - Fork 11
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
Migrate from Laravel Mix to Vite #2228
Conversation
❌ Shift did not remove some of the previous npm scripts running |
ℹ️ Previously, Laravel configured several npm scripts for building assets. For Vite, Laravel configures a Shift automated this change by replacing commands using these scripts with their new Vite script. However, you may still be referencing these scripts in your code or in deployment scripts. |
Shift removed your CSS entry point from your Vite configuration. However, you will need to import this CSS in your JavaScript entry point. |
ℹ️ Laravel renamed the environment variables used by Mix to use a |
ℹ️ Vite requires JavaScript files containing JSX to have a |
If you wish to track the generated frontend assets within your project, such as for ease of deployment, you may undo this commit by running: |
|
ℹ️ The new If you experience JavaScript errors relating to undefined references, you may need to reorder your scripts or add the |
⚗️ This Shift is still being refined. Please report any issues or suggestions to [email protected]. Your feedback is what helps improve the experience for everyone. |
This pull request includes changes for migrating from Laravel Mix to Vite outlined in Migration Guide and automated by the Vite Converter.
Before merging, you need to:
shift-117022
branchcomposer update
npm install
Please send your feedback to [email protected] or share the good vibes on Twitter.