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
I am wondering if it would make sense to extract the vue file processing into a separate module, so that other tools could benefit from the existing solution in vue-jest as well. Right now there a several different modules handling the parsed output from vue-template-compiler (vue-jest, vue-loader, vueify or jest-vue-preprocessor).
Background: I am currently working on a project that needs to consume vue files independent from a concrete implementation (like processing via vue-loader or vueify) and came here, because vue-jest does exactly what I would need. But of course vue-jest does not expose the processing functionality, because it serves another purpose.
Does this make sense?
The text was updated successfully, but these errors were encountered:
I am wondering if it would make sense to extract the vue file processing into a separate module, so that other tools could benefit from the existing solution in vue-jest as well. Right now there a several different modules handling the parsed output from vue-template-compiler (vue-jest, vue-loader, vueify or jest-vue-preprocessor).
Background: I am currently working on a project that needs to consume vue files independent from a concrete implementation (like processing via vue-loader or vueify) and came here, because vue-jest does exactly what I would need. But of course vue-jest does not expose the processing functionality, because it serves another purpose.
Does this make sense?
The text was updated successfully, but these errors were encountered: