weex-vue-framework is a package that provides the Vue 2.0 framework for use with Weex, a platform enabling developers to build Android, iOS, and Web apps from a single codebase using modern web development skills. This package is an "auto-generated" component of the Vue.js ecosystem, specifically tailored for the Weex environment. The current stable version of the underlying Vue 2 series is 2.7.16, known as "Swan Song", which marked the final official release for Vue 2. It reached its End of Life (EOL) on December 31st, 2023, meaning it no longer receives new features, updates, or official security fixes. As such, this package, being intrinsically tied to Vue 2, is effectively deprecated. Its primary differentiator is its role in enabling Vue 2 applications to render natively on Weex-powered mobile environments, extending Vue's capabilities beyond the browser to native UI rendering.
npm install weex-vue-frameworkVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates a basic Vue 2 Single File Component (SFC) designed for a Weex environment. It shows a simple counter with reactive data and a method to update it, along with Weex-specific styling considerations like explicit dimensions. The `main.js` illustrates the entry point, including the Weex framework annotation and the instantiation of the Vue root component. This setup assumes `weex-vue-framework` is providing the underlying Vue 2 runtime when `import Vue from 'vue'` is called within a Weex project context.
Migrate your application to Vue 3 or consider purchasing Never-Ending Support (NES) for Vue 2 from HeroDevs to receive ongoing security patches and compatibility fixes.
Consult the official Weex documentation and Vue 2 Weex integration guides for best practices on project setup and dependency management. Avoid trying to update or manage this package as a standalone Vue library unless explicitly directed by Weex documentation.
For new Weex projects, explore if Weex officially supports Vue 3 or alternative modern frameworks. For existing projects, plan for a migration or assess the risks of continuing with an unmaintained framework.
Always use single-file components (`.vue` files) and ensure your Weex build setup includes a template compiler (like `weex-loader`) that transforms templates into render functions before deployment. Define components using `render` functions directly if not using SFCs.
Ensure your entry file includes the `// { "framework": "Vue" }` comment or `"use weex:vue";` directive prologue at the very top, depending on your Weex SDK version. Verify that Weex-related build tools (e.g., `weex-toolkit`, `weex-loader`) are correctly installed and configured.Ensure all Vue components are defined as Single File Components (`.vue` files) and that your build process (e.g., Webpack with `weex-loader`) is correctly configured to pre-compile these templates into `render` functions. Do not use inline templates or `Vue.compile` in your runtime code.
Verify that the native module 'xxx' is properly implemented and registered within your Android and iOS Weex projects. Check for case sensitivity or naming mismatches. Ensure your Weex SDK version supports the module or that any custom native modules are linked correctly.
This is a warning, not an error preventing compilation. The official fix is to migrate your project to Vue 3. If migration is not immediately feasible, you can explore Vue 2 Never-Ending Support (NES) from HeroDevs for continued security updates, or suppress the warning at your own risk.
No dependency data recorded yet.