Meituan-Dianping/mpvue · info
[Vue tip]: ${msg}
Error message
[Vue tip]: ${msg} What it means
This is not an error but a tip: the compiler's tip() helper prints [Vue tip]: <msg> via console.warn when a console exists and config.silent is false. Tips convey non-critical developer guidance during compilation, unlike warn() which prints [Vue warn] via console.error.
Source
Thrown at packages/weex-template-compiler/build.js:954
var hasConsole = typeof console !== 'undefined';
var classifyRE = /(?:^|[-_])(\w)/g;
var classify = function (str) { return str
.replace(classifyRE, function (c) { return c.toUpperCase(); })
.replace(/[-_]/g, ''); };
warn$1 = function (msg, vm) {
var trace = vm ? generateComponentTrace(vm) : '';
if (config.warnHandler) {
config.warnHandler.call(null, msg, vm, trace);
} else if (hasConsole && (!config.silent)) {
console.error(("[Vue warn]: " + msg + trace));
}
};
tip = function (msg, vm) {
if (hasConsole && (!config.silent)) {
console.warn("[Vue tip]: " + msg + (
vm ? generateComponentTrace(vm) : ''
));
}
};
formatComponentName = function (vm, includeFile) {
if (vm.$root === vm) {
return '<Root>'
}
var name = typeof vm === 'string'
? vm
: typeof vm === 'function' && vm.options
? vm.options.name
: vm._isVue
? vm.$options.name || vm.$options._componentTag
: vm.name;
var file = vm._isVue && vm.$options.__file;View on GitHub (pinned to 6c5d78ee04)
Solutions
- Read the tip text after the prefix and apply the suggested guidance
- Set Vue.config.silent = true to suppress tips and warnings
- Filter console.warn output prefixed with [Vue tip] in CI logs
Example fix
// before // console noise from tips during compile // after Vue.config.silent = true; // suppresses [Vue tip]/[Vue warn] output
Defensive patterns
Strategy: validation
Validate before calling
if (!Vue.config.silent && process.env.NODE_ENV === 'production') {
Vue.config.silent = true; // suppress dev tips in production builds
} Prevention
- Treat [Vue tip] output as guidance, not failure
- Set Vue.config.silent = true in CI to keep logs clean
- Read the message body after the prefix before changing code
When it happens
Trigger: Any compilation path that calls tip(msg, vm) in development mode with config.silent === false and a working console; the tip text follows the prefix in the message.
Common situations: Seeing dev-time guidance messages in the console during template compilation; developers sometimes mistake them for errors or want to suppress them in noisy CI logs.
Related errors
- tag <${tag}> has no matching end tag.
- passive and prevent can't be used together. Passive handler
- Templates should only be responsible for mapping the state t
- <template> cannot be keyed. Place the key on real elements i
- Invalid v-for expression: ${exp}
AI-assisted analysis of Meituan-Dianping/mpvue@6c5d78ee04 (2026-09-02).
Data as JSON: /api/errors/52352b643c9f2513.
Report an issue: GitHub.