Hmmm... I guess the shorthand is only for Component-based projects then. I will clarify that in the spec.

Same for Vue.require: Vue.require('utils') only works because it has already been called in a static way: https://github.com/yyx990803/vue/blob/master/src/main.js#L3

A (really ugly) solution could be to require all the modules relevant for plugins in main.js…

Yeah this is actually one of the reasons I use Component over Browserify... let me think about this.

Maybe a dedicated plugin API could be provided (and documented), instead of exposing all the internal components:

// plugin-api.js
module.exports = {
    utils: require('./utils'),
    // relevant modules
}

// main.js
var pluginApi = require('./plugin-api')
ViewModel.require = function (path) {
    return pluginApi[path]
}

You could try commonjs-everywhere

I'm actually thinking of shipping built versions for npm instead. This would allow me to get rid of the emitter hack and also split observer into its own package.

Scrap that - browserify attempts to parse all the requires inside and throws compile time error.

Yup, Browserify attempts to parse on bundle, making dynamic paths
impossible. For the likes of utils, or any other static named module
without './', you can define a list of modules in package.json,

browser : {
  "utils" : "./deps/utils"
}

etc.

On Fri, Feb 21, 2014 at 8:56 PM, Evan You notifications@github.com wrote:

Scrap that - browserify attempts to parse all the requires inside and
throws compile time error.

Reply to this email directly or view it on GitHubhttps://github.com/yyx990803/vue/issues/124#issuecomment-35772711
.

So here's all modules that are exposed for plugins: utils, config, transition, observer. These are theoretically all you need. Plugins should not mess with the other parts anyway. Docs will be updated together with the next release when the plugin spec is more mature.

I think it may also true for a require.js setup when you use the almond shim.

Vue.require() doesn't work with component/builder2 (used in component@1.0.0). With builder2, require() calls are overwritten during the build step.

For instance

var utils = require('./utils')
// become
var utils = require("yyx990803~vue@v0.10.5/src/utils.js")

Could be fixed like @bpierre has suggested:

var modules = {
  utils: utils,
  config: config,
  transition: require('./transition'),
  observer: require('./observer')
};

ViewModel.require = function (path) {
    return modules[path]
}

yeah, that might be the better way to go. open to PRs!