next-contentlayer: BREAKING Change withContentlayer API and introduce createContentlayerPlugin

[schickling]

Given many users are intuitively using the withContentlayer API "directly" as a Next.js plugin as opposed to "calling it" before using, I'm proposing to change the withContentlayer API to the following:

Before

import { withContentlayer } from 'next-contentlayer'

//                             ▼▼
export default withContentlayer()({
  // Your Next.js config...
})

After

import { withContentlayer } from 'next-contentlayer'

//                            ▼▼▼ no additional `()` needed
export default withContentlayer({
  // Your Next.js config...
})

Additionally there will also be a createContentlayerPlugin API which allows for providing some non-default Contentlayer configuration options:

import { createContentlayerPlugin } from 'next-contentlayer'

const withContentlayer = createContentlayerPlugin({
  // Additional Contentlayer config options
})

export default withContentlayer({
  // Your Next.js config...
})

[schickling]

This was just released as part of the new 0.2.1 version. 🚀

Feel free to comment in case you're running into any problems or open a new issue.