Closed ErKeLost closed 11 months ago
Oh, you're quite right! I usually test with cargo t
, and the test you fixed is for the NAPI integration. I only check that NAPI builds and benches.
Yeah, adding the test pipeline would be great. Maybe it can be a phase in the playground
workflow? I am not really familiar with GitHub CI and if it's a good idea tbh.
What do you mean by "Farm CI"?
Oh, you're quite right! I usually test with
cargo t
, and the test you fixed is for the NAPI integration. I only check that NAPI builds and benches.Yeah, adding the test pipeline would be great. Maybe it can be a phase in the
playground
workflow? I am not really familiar with GitHub CI and if it's a good idea tbh.What do you mean by "Farm CI"?
I'm sorry I didn't make it clear. What I meant was that github ci was used to run some necessary tests to prevent unpredictable problems when merging the code. anyway, I think we may access unplugin in the future, so napi should also add js's test guarantee coverage.
Recently, I am also studying the vue compiler, and I would like to study with you if I can.
Farm will be online soon, and 1.0 is looking forward to your plug-in as the official vue plug-in of farm.
Thanks, I'll take a look at farm's workflows when I have a chance.
I can help you with the Vue compiler internals. Which one are you interested in? :smile:
The official one is technically a parser plus RegEx rewriter, which has its pros and cons (historically lots of cons). And it also has a ton of documentation. The best place to start is https://play.vuejs.org, which I personally use quite a lot.
This project, on contrary, intends to be a "proper" compiler/optimizer without cutting any corners. Something which the official compiler is slowly evolving to.
Regarding Farm plugin, it is tempting indeed, yet I think fervid
is not close for its 1.0
. Even if the functionality is covering 95% of my usecases, it's only 70% ready for production use.
There are also some DX features planned which the official compiler does not support, but fervid
will to make it stand to its "All-in-One" promise. Native integration with Farm is one of such features :wink:
Thank you for your suggestion. I will follow your way to learn the compiler of vue
. I am very interested in fervid
. I am also looking forward to fervid's dx
plan and hope to integrate it into farm
as soon as possible. Thank you. I also hope that I can learn something about the compiler and finally, if possible, I can help you to develop together. Thank you very much for your reply
As for the problem that what you said is not applicable to production, I think we can provide a basic plug-in for users to experience in the development environment first, and the production environment can be switched to a part of the existing js plug-in, so that users can use it in advance and find more problems. What do you think?
Hi @ErKeLost :wave:
How interested are you in contributing to this project? I am a bit wound up with inline mode (this is an optimized mode of compiling SFC when you use <script setup>
) and don't have time to implement farm
s CI atm :( But I checked it, it's pretty smart!
To you and anyone interested, I really do appreciate if someone could guide me through setting it up. There are also tests to correct, since I implemented a new parser and it does some things better (notably #6).
I am very willing to help with your project and I am very interested in it. I will go back and try to migrate github ci for our project first.