fix: resolve merge conflicts for v1.1.0-a release #164
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Resolves merge conflicts between
mainanddevbranches for the v1.1.0-a release, prioritizing code from thedevbranch to preserve bun/vite migration and mobile responsive features.Related Issue
Closes #150
Type of Change
Changes Made
mainintodevbranchpackage.json(kept vite devDependencies, removed webpack)package-lock.json(bun uses bun.lock)src/files from dev branch to preserve:Screenshots (if applicable)
N/A
Checklist
npm run format:fixandnpm run lint:fixnpm run typecheckwith no errorsnpm run test:runAdditional Notes
This PR ensures that the
devbranch code takes priority overmainbranch code, preserving all the recent work on bun/vite migration and mobile responsive features.