Missing property server.views

[vitaliyAtSvarog]

var Hapi = require('hapi');
var server = new Hapi.Server();

server.connection({
    port: cfg.port,
    host: cfg.host,
    routes: {
        cors: true
    }
});

server.views({
    engines: {
        'slm': require('slm')
    },
    basePath: __dirname + '/backend/views',
    compileOptions: {
        basePath: __dirname + '/backend/views',
        useCache: cfg.useCache // disable internal cache - useful for development
    },
    isCached: cfg.useCache // disable hapi view cache
});

then in console write 'node server.js' and get error http://screencast.com/t/TfZQLTbb

see debug

[gergoerdosi]

You need to register the vision plugin if you use hapi 9.x.x.

server.register(require('vision'), function (err) {
    if (err) {
        throw err;
    }

    server.views({ ... });

    server.start(function () {
        server.log('info', 'Server running at: ' + server.info.uri);
    });
});

[vitaliyAtSvarog]

Is that described somewhere in the documentation?

[gergoerdosi]

Not yet, the documentation needs an update.

[vitaliyAtSvarog]

gergoerdosi thx. You helps me 👍

[AdriVanHoudt]

@vitaliyAtSvarog read #2682

[dlong500]

Yeah, the documentation and plugins page really need updating. Even though I specifically read about the breaking changes in the v9.0.0 release notes it still took me a while to figure out what to actually DO to migrate the code. In addition to registering the newly separated plugins, you also have to actually install them via npm (and even then it is somewhat obscure, because the plugin names aren't prefixed with hapi--instead it's just vision and inert). They aren't even listed on the "Plugins" page at the site yet either.

With as rapid as updates are for hapi, wouldn't it be better to have some type of versioned documentation like MySQL? I know that a lot of the coders have more important things to do than update documentation, but it's definitely important. I'd volunteer myself but I'm not an expert at even just using hapi yet...

_EDIT_ When I mentioned versioned documentation, I do realize the API docs are versioned, but it would be useful to have a similar model for other parts of the site like plugins (especially when a particular plugin doesn't even apply or make sense before or after a certain version).

[hueniverse]

This is the first breaking release since last December. I wouldn't call it rapid.

[dlong500]

Sorry, I didn't mean to imply there are breaking changes all the time. But I'd still call going from version 2.x to 9.x in the past year and a half a fairly rapid pace. Even if changes aren't breaking it could still be somewhat difficult to stay on top of things without really good documentation.

That being said I'd much rather have the type of stellar development that has been going on than to have awesome documentation with a stagnant framework. So thanks for your work.