feat: vite frontend pages build - #536
Draft
storycraft wants to merge 7 commits into
Draft
Conversation
… system * Vite build system for pages. * Remove page build scripts and deps from `@tosu/server`. * Use vue package.
storycraft
marked this pull request as draft
January 23, 2026 03:52
This comment was marked as outdated.
This comment was marked as outdated.
| .forEach((i) => i.addEventListener('change', () => checkSettingsChanges())); | ||
|
|
||
| const isNumberValid = (num) => { | ||
| if (typeof num === 'number') return num - num === 0; |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@tosu/pages, setup Vite build system.assetsfrom@tosu/serverto@tosu/pages.vue(3.5.24) package.@tosu/server.tscbuild in@tosu/updaterrun:devnot showing pages correctly since feat: remove build steps for internal packages #528.This is prerequisites for rewriting frontend in issue
For assets, internal assets are located in
assetsdirectory and public files are located inpublic. You may access them via@assetsand@public.Existing js codes for frontend are still excluded from eslint target. No code changes except vue import.