Skip to content
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.

Sign up for GitHub

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 typos in v4 migration doc #33

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix typos in v4 migration doc #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Migration from v4

- Vitreum will no longer do file system anaylsis to automatically include style files. Each jsx component must now `require` in it's associated `less` file
- Vitreum will no longer do file system anaylsis to automatically include style files. Each jsx component must now `require` in its associated `less` file
- Vitreum can now be used as a commandline tool, so you can remove your build scripts and use npm scripts instead.
- Asset files will now not be automatically required, so you must use `require` statements to let vitreum know which asset files it should consider.
- The `dev` process now "builds" a lot less, it's now more focused on iterative code and style development. So make sure to run a `build` step before you `dev`
- Server watching is now done through dependacy analysis of your `main` file outlined in the `package.json`, so depending on how your backend is setup, some files might not trigger a automatic server restart during a `dev` step
- Server watching is now done through dependency analysis of your `main` file outlined in the `package.json`, so depending on how your backend is setup, some files might not trigger a automatic server restart during a `dev` step