Error with ejs-mate: cb is not a function about point-of-view HOT 8 CLOSED

@cemremengu Sorry, missed the comment. I ended up having to fork both point-of-view and ejs-mate. The way it was setup locals were not being properly propagated, I ended up adding a couple more features, meaning it might not be a straight PR to either project.

from point-of-view.

Hello!
I think you try use ejs engine for ejs-mate

I had same problem with this code:

fastify.register(require('point-of-view'), {
    engine: {
      ejs: require('ejs-mate')
    },
    includeViewExtension: true,
    templates: './templates',
    options: {
      filename: resolve('templates')
    }
  });

Then i change engine ejs to ejs-mate and now its working:

  fastify.register(require('point-of-view'), {
    engine: {
      'ejs-mate': require('ejs-mate') // here need set 'ejs-mate'
    },
    includeViewExtension: true,
    templates: './templates',
    options: {
      filename: resolve('templates')
    }
  });

from point-of-view.

I will take a look at this, unfortunately it supports only version 2.3.0 atm

from point-of-view.

@goliatone if you would like to submit a PR I will take at as well :)

from point-of-view.

@TheRTK it would not surprise me that I made a silly mistake like that. However, I wanted to add support for some features I had in my previous setup like being able to resolve views from different view folders, a better way to manage locals (config file with locals per route, defaults, merging, etc). Thanks for the heads up tho!

from point-of-view.

Hello all, any progress on this?

Could I suggest a reference to requiring 2.3.0 is added to the readme?
I spent about half an hour trying to figure out why it wasn't working, including reading this thread twice, before realising that the sample @TheRTK provided as "working" was only "working" on the 2.3.0 branch

from point-of-view.

Improving the readme is always a good idea! Would you like to add this?

There is a PR #81 to discuss to update to ejs-mate 3.0.0 but seems stalled due to the project inactivity.

from point-of-view.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from point-of-view.