Cannot read property 'Symbol(Symbol.iterator)' of path.match

[awulkan]

I installed the starter template and ran npm run dev to get this error below.

NuxtServerError

Module build failed: TypeError: Cannot read property 'Symbol(Symbol.iterator)' of path.match at
 getSection (C:\Users\USER\Desktop\vue\nuxtent\my-
site\node_modules\nuxtent\dist\loader.js:19:33) at Object.module.exports
 (C:\Users\USER\Desktop\vue\nuxtent\my-
site\node_modules\nuxtent\dist\loader.js:114:19)

node_modules\nuxtent\dist\loader.js
}

const getSection = path => {
  // capture '/content/closestSubsection' or  '/content'
  // eslint-disable-next-line no-unused-vars
  const [match, section] = path.match(/\/content([/][a-zA-Z\-_]*|$)/)
  return section === '' ? '/' : section
}

const getComponentBaseName = (baseDir, name, extensions) => {
  const baseName = join(baseDir, name)

Js
getSection@19:33

Windows 10
Node 8.9.1
Latest Nuxtent version

_{This question is available on Nuxt.js community (#c104)}

[sebtiz13]

Duplicate #94
You do compile module from branch master

[awulkan]

@sebtiz13 So I can't install it through npm? I'm not sure I understand.

[sebtiz13]

@awulkan Exactly the version released on npm doesn't work on windows.
You do to wait a new release on npm or compile manually the package from branch master.
The bug is solved but i don't know why the new version is not released.

[awulkan]

@sebtiz13 Ok, thanks. I will just use another generator for now then. Maybe I'll come back to this once it's released.

[awulkan]

Why was this reopened if it's already solved?

[alidcast]

Sorry, I've been incredibly busy but I know that people use this plugin for their blogs and do intend to publish the working windows version at some point (just need to make sure it doesn't break anything etc.). I reopened it as a reminder.