Opinionated Nuxt + Craft boilerplate.

1. Copy the scaffold contents to your project
2. Make a package.json that includes Nuxt and Cloak: yarn add nuxt @bkwld/cloak

From your project's nuxt.config.coffee:

# Make boilerplate, setting some options
{ mergeConfig, makeBoilerplate } = require '@bkwld/cloak'
boilerplate = makeBoilerplate
  siteName: 'My Site'
  pageTypenames: ['towers_towers_Entry']

# Merge project specific config with cloak boilerplate
module.exports = mergeConfig boilerplate,

  # Append additional internal routes for vue-routing-anchor-parser
  anchorParser: internalUrls: [
    /^https?:\/\/(www)?\.domain\.com/
  ]

  # Customize routes
  router: extendRoutes: (routes, resolve) ->

    # Make all path params required in detail routes
    detailRoutes = ['blog-tag-tag', 'blog-category-article']
    routes.filter ({ name }) -> name in detailRoutes
    .forEach (route) -> route.path = route.path.replace /\?/g, ''

    # Append routes from boilerplate
    return boilerplate.router.extendRoutes routes, resolve

These are options you can pass to makeBoilerplate. See the source code for defaults.

Besides providing a bunch of nuxt.config boilerplate, this project also provides these shared resources:

• components - Vue components that are already setup for autodiscovery with no prefixing.
• fragments - GraphQL fragments for common objects
• mixins - Vue mixins
• services - Libraries of methods that can be imported into your code and which are also injected globally. For example, @$craft and @$defer are available in all components.

• Using cjs module syntax for to make developing via yarn link simpler. I tried using esm package but it ran into issues with imports of imports.
• Using a fork of webpack-graphql-loader to work around issues with the loader not being found from the root package. I think because it referenced some old and unecessary deps.
• Use the Page View dataLayer event for firing Page View style tags from GTM