You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our setup, we much prefer the "raw" .js files over "proprietary" formats like .sfc, exactly because they do not require a build step.
This way, what one sees in the editor is exactly what goes to the browser, and there is no need to teach tooling/syntax coloring etc. about yet another specialised file format.
However, it seems that this style of working is slowly going down the drain🤔 For example, the new defineModel() macro for v-model does not describe the 'setup()' way at all. Just a vague (and collapsed) "Pre 3.4" paragraph.
Also, the documentation states that SFC files are "recommended", but does not (yet?) say that no-build-step workflows are "deprecated".
I think Vue overall is awesome (and thanks!), but what to expect?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello
In our setup, we much prefer the "raw" .js files over "proprietary" formats like .sfc, exactly because they do not require a build step.
This way, what one sees in the editor is exactly what goes to the browser, and there is no need to teach tooling/syntax coloring etc. about yet another specialised file format.
However, it seems that this style of working is slowly going down the drain🤔 For example, the new defineModel() macro for v-model does not describe the 'setup()' way at all. Just a vague (and collapsed) "Pre 3.4" paragraph.
Also, the documentation states that SFC files are "recommended", but does not (yet?) say that no-build-step workflows are "deprecated".
I think Vue overall is awesome (and thanks!), but what to expect?
Thanks in advance
/Flemming
Beta Was this translation helpful? Give feedback.
All reactions