Repository navigation
Building Misskey with Vize #71
kakkokari-gtyih
started this conversation in
General
Replies: 19 comments 19 replies
|
I'll improvement on misskey and elk, thanks |
0 replies
|
Tried v0.10.0 (with vite v8 beta 16) and the errors decreased down to 2! Good work! Logs |
1 reply
|
FYI - just tried out v0.11.0 and the errors stays the same (maybe I'm just failing to update dependencies properly though) |
|
Update to v0.15.0 - and finally went through all of the build process! It seems there's an issue with the v-deep selector. While it's unclear at which layer this error was introduced, I think it's worth noting. Log |
0 replies
|
Updated to v0.25.0 and I tried building and launching Misskey built with Vize. Here's what I achieved and stumbled:
*Slots on some components are rendered as normal HTML slot tag*
|
0 replies
|
Just tried v0.62.0 (sorry for absence - i was busy bundling backend with rolldown!) Build failed with this setup (in <template>
<Comp v-model="reactiveObject" />
</template>
<script lang="ts" setup>
import { reactive } from 'vue';
const reactiveObject = reactive({ foo: 'bar' });
</script>That said, I think our use case is an edge case and it somehow works with the current compiler, so I treated this as a user code issue and replaced it with Time directly reported by vize plugin is [
{
"transform": {
"invokeCount": 2520,
"totalTime": 219
},
"resolveId": {
"invokeCount": 5106,
"totalTime": 648330
},
"name": "vite-plugin-vize",
"enforce": "pre"
},
{
"transform": {
"invokeCount": 1485,
"totalTime": 28
},
"resolveId": {
"invokeCount": 0,
"totalTime": 0
},
"name": "vize:post-transform",
"enforce": "post"
}
]Nested routes are now working properly. However, some styles of component are missing: 
Also, widgets are still not working. |
1 reply
|
|
Just tried v0.65.0:
After transformation by vize, vite (lightningcss) emitted some errors which doesn't appear with normal vite vue plugin: long logTime directly reported from vize plugin is [
{
"transform": {
"invokeCount": 2520,
"totalTime": 125
},
"resolveId": {
"invokeCount": 5106,
"totalTime": 311003
},
"name": "vite-plugin-vize",
"enforce": "pre"
},
{
"transform": {
"invokeCount": 1485,
"totalTime": 22
},
"resolveId": {
"invokeCount": 0,
"totalTime": 0
},
"name": "vize:post-transform",
"enforce": "post"
}
]
|
0 replies
|
Tried v0.75.0 and this has introduced some regression: Some slots (left, tabs) on page header (MkPageHeader) is not working 
The correct UI should look like this: 
|
7 replies
|
Updated to v0.108.0 and the issue still present 
|
|
Found out that some of these components are using SCSS for styling. Maybe that breaks something? |
|
I'll check! |
|
Thanks for the detailed report. I tracked this to slot outlet codegen in control-flow/list paths: direct Fixed in #578, now merged. I verified the Misskey fixture (583 Vue files) and Elk fixture (253 Vue files) compile without any remaining The old |
|
Follow-up: I also fixed the scoped CSS side in #579. Legacy deep/global selectors such as This is included in |
|
Just updated to v0.116.0 and found two problems with deeper investigation:
|
0 replies
|
I've shipped some fixes at https://github.com/ubugeeei/vize/releases/v0.117.0 |
3 replies
|
Just tried v0.117.0 and it imports |
|
It seems v-bind in style issue... I'll check it...! |
|
Just tried v0.118.0 and still failing parsing some tricky use of CSS 
|
1 reply
|
Thanks again for the concrete repro. I fixed this in #602, and it has been merged after CI passed. The CSS |
|
Just tried v0.124.0 and it fixed most of the design issues! However we still have tricky case around v-bind css: This component has This component also have Maybe there is some conflicts applying styles. Vize: Correct: |
1 reply
|
fixed |
|
🎉 |
0 replies
|
Just tried vize 0.155.0 and the things improved dramatically 🎉
|
2 replies
|
related: #883 |
|
Thank you - will check back soon! |
|
Tried v0.174.0 - most of features are now working with some edge cases left!
|
1 reply
|
I confirmed that the first two of the issues are fixed! I'm not come across the last one so far. |
|
Latest metrics: [
{
"transform": {
"invokeCount": 2579,
"totalTime": 58
},
"resolveId": {
"invokeCount": 0,
"totalTime": 0
},
"name": "vize:post-transform",
"enforce": "post"
},
{
"transform": {
"invokeCount": 2579,
"totalTime": 88
},
"resolveId": {
"invokeCount": 0,
"totalTime": 0
},
"name": "vize:style-post-transform"
},
{
"transform": {
"invokeCount": 3633,
"totalTime": 507
},
"resolveId": {
"invokeCount": 5348,
"totalTime": 927413
},
"name": "vite-plugin-vize",
"enforce": "pre"
},
]Comparison - [
{
"transform": {
"invokeCount": 2653,
"totalTime": 3355
},
"resolveId": {
"invokeCount": 0,
"totalTime": 0
},
"name": "vite:vue"
},
] |
2 replies
|
The |
|
The plugin I use is |
|
I am starting to test Vize Canon type checking now. I am already seeing a lot of errors and am currently investigating them. I will provide a minimal reproduction as soon as possible, but to speed up the process, I have pasted the error logs below (note that I'm still adjusting configuration, so there may be some false-positives): I have also already created an issue with a minimal reproduction, so please take a look #1726 Logs |
0 replies
|
#1726, #2011 and #2012 are confirmed to be resolved! I still got a lot of error from Logs |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I tried out building frontend of Misskey using Vize and Vite 8 beta, and build failed.
Although Misskey is doing some unusual modification before and after the process, but the frontend app successfully built with
@vitejs/plugin-vuehttps://github.com/kakkokari-gtyih/misskey/tree/experimental-vite8-vize
Logs
Any comments or suggestions are appreciated! Thank you for making such an anbitious tool chain!
All reactions