Hi! I really enjoy exploring both nuxt & nuxtent-module! I ran into an issue that I have a hard time figuring out. I use yarn generate on the production host (I use netlify) to generate the site, everything builds fine and goes live.

The problem: For example, I have a nuxt-link to content (blog post) /blog/first-blog which is the perma-link https://www.mysite.com/blog/first-blog (if you copy the link) for this particular content. If i click on it it results in an error:

Failed to load https://mysite.com/_nuxt/content/blog/blog.first-blog.json: Redirect from 'https://mysite.com/_nuxt/content/blog/blog.first-blog.json' to 'https://www.mysite.com/_nuxt/content/blog/blog.first-blog.json' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://www.mysite.com' is therefore not allowed access.

However if I just copy paste the same link to the browsers url field and press enter, it works fine and displays my blogpost.

On my dev server localhost:3000/content-api does work but in production, https://www.mysite.com/content-api does not exist if I try to visit it, is it supposed to be this way since I use yarn generate to build the website?

content folder:

/content
    /blog
      2019-08-27-first-blog.md
    /nyheter
      2019-08-28-hello-news.md

nuxtent.config.js:

module.exports = {
    content: [
        ['blog', {
            page: '/blog/_blogpost',
            permalink: 'blog/:slug',
            generate: [
                'get',
                'getAll'
            ]
        }],
        ['nyheter', {
            page: '/nyheter/_newspost',
            permalink: '/nyheter/:slug',
            generate: [
                'get',
                'getAll'
            ]
        }],
    ],
    api: {
      baseURL: 'http://localhost:3000',
      browserBaseURL: 'https://mysite.com'
  }
}

Appreciate any input I can get on this :) I feel like I have read everywhere but did not find anything that could fix this issue.

Version

development

Reproduction link

http://infiniti.dinamo.mx/

Steps to reproduce

Run yarn dev and using markdown components

What is expected ?

Run without problems, even in threaded mode

What is actually happening?

There is a weird message when using nuxt-edge that appears when runing in dev mode complaining about not finding a markdown module. This breaks threaded mode

Version

1.4.1

Reproduction link

https://codesandbox.io/s/vue

Steps to reproduce

• Create a folder without an index.md, index.comp.md inside or a [foldername].comp.md, [foldername.md] at the same level

What is expected ?

Just to work without index or to display an informative error that either of those options are needed (index or same name)

What is actually happening?

throws a "Atributes not found"

Version

1.4.1

Reproduction link

https://nuxtent.now.sh/

Steps to reproduce

VIsit https://nuxtent.now.sh/

What is expected ?

Online documentation to be available.

What is actually happening?

Getting 402 payment required

Is the nuxtent-module supposed to generate static pages with nuxt generate? Or do I still have to manually configuration this in nuxt?

Based on the documentation, nuxtent-module should generate static pages.

I have a configuration like this:

module.exports = {
  api: {
    baseURL: process.env.NODE_ENV === 'production'
      ? 'http://myproductionsite.com'
      : 'http://localhost:3000'
  },
  content: {
    page: '/_page',
    permalink: ':slug',
    isPost: false
  }
}

A _page.vue file along with an index.vue file in the pages folder and a bunch of markdown files in the content folder directly.

In development mode, everything works fine. But the output of nuxt generate does not create any other HTML files except index.html. The pages are only available in .js file format.

So just before I search for any error I want to make sure, I have the correct expectations of the nuxtent-module.

Hi,

I'm getting the following error on run dev

This dependency was not found:

• /Users/projets/my-site-nuxtent/.nuxt/client.js in multi webpack-hot-middleware/client?name=client&reload=true&timeout=30000&path=/_webpackhmr ./.nuxt/client.js

My posts look like this

['posts', { page: '/posts/_slug', permalink: '/:year/:month/:day/:slug', isPost: true, generate: ['get', 'getAll'] }]

Now I want my permalinks not to look like this /2018/05/28/2018-05-28-lorem-ipsum but instead like this /2018/05/28/lorem-ipsum how do I make this happen?

Version

1.4.1

Reproduction link

https://github.com/nuxt-community/nuxtent-module/tree/master/examples/sitemap

Steps to reproduce

Checkout sitemap example project, yarn && yarn generate

What is expected ?

A generated sitemap.xml

What is actually happening?

Error: connect ECONNREFUSED 127.0.0.1:3000

Hi there, I'm using the versions as shown below. Whenever I access the pages that has get() or getAll(), my nuxt will fall into infinite loading.

package.json

  "dependencies": {
    "nuxtent": "^1.4.1",
    "nuxt": "latest",
    "@nuxtjs/axios": "latest"
  },

components

export default {
  asyncData: async ({ app, route, payload }) => ({
    post: payload || (await app.$content("/").getAll())
  })
};

console

  nuxt:render Rendering url /? +2ms
  nuxt:render Rendering url /? +1ms
  nuxt:render Rendering url /? +3ms
  nuxt:render Rendering url /? +1ms
  nuxt:render Rendering url /? +3ms
  nuxt:render Rendering url /? +1ms
  nuxt:render Rendering url /? +3ms
  nuxt:render Rendering url /? +1ms

P/S: I'm using Mac OS X, but I'm sure there are no .DS_Store hanging around project folder.

What problem does this feature solve?

it solve big data in a blog list

What does the proposed changes look like?

front-matter change to gray-matter that already has excerpt option

Halo, is there a plan to use gray-matter instead of front-matter as it feature is promising?

I would like to use yaml functionality to just expose data through the API. However, I don't want to generate individual pages for each of those yaml files inside of a folder.

What is the best way to go about this?

Hello!

I currently try to implement nuxtent into my nuxt project on a windows machine.
I followed the docs carefully but couldn't get it to run.

It seems in the current code, join from nodes path api is used. This should not be used for joining URLs (on windows, you will get URLs with double backslashes).
We could implement this https://github.com/jfromaniello/url-join to join the urls or try to use nodes url.resolve.

I can try to fix this tomorrow and send in a pull request, if you guys want me to.

First of all, thanks for making such an amazing module. I am trying to use nuxtent-template as mentioned in the demo and getting below error when trying to access post page.
Request failed with status code 404. I have tried as explained in issue https://github.com/nuxt-community/nuxtent-module/issues/53 but didn't help.

Below are my files.

package.json

{
  "name": "my-site",
  "version": "1.0.0",
  "description": "Nuxt.js Content Site",
  "author": "",
  "private": true,
  "dependencies": {
    "nuxtent": "latest",
    "nuxt": "^1.0.0-rc11",
    "@nuxtjs/axios": "latest"
  },
  "scripts": {
    "dev": "nuxt",
    "build": "NODE_ENV='production' nuxt build",
    "start": "NODE_ENV='production' nuxt start",
    "generate": "NODE_ENV='production' IS_STATIC=true nuxt generate",
    "lint": "eslint --fix --ext .js,.vue --ignore-path .gitignore .",
    "deploy": "push-dir --dir=dist --branch=gh-pages --cleanup",
    "precommit": "npm run lint"
  },
  "devDependencies": {
    "babel-eslint": "^7.1.1",
    "eslint": "^3.15.0",
    "eslint-config-standard": "^6.2.1",
    "eslint-loader": "^1.6.1",
    "eslint-plugin-html": "^2.0.0",
    "eslint-plugin-promise": "^3.4.1",
    "eslint-plugin-standard": "^2.0.1"
  }
}

nuxtent.config.js

module.exports = {
  content: {
    permalink: ':slug',
    page: '/_content',
    isPost: false
  },

  api: {
    baseURL: process.env.NODE_ENV === 'production'
      ? 'https://admiring-kowalevski-d1e6e6.netlify.com'
      : 'http://localhost:3000'
  }
}

Screenshot of the page. Let me know if you need any other information.

Version

1.4.1

Reproduction link

https://github.com/Gingernaut/gingernaut.github.io/tree/dev

Steps to reproduce

Extending the markdown parser in my nuxtent.config.js does not work, using the Prism.js configuration at https://nuxtent.now.sh/guide/configuration#parser-options.

My entire nuxtent config:

const Prism = require('prismjs')

module.exports = {
  content: [
    ['blog', {
      page: '/blog/my-article',
      permalink: '/blog/:slug',
      isPost: true,
      generate: [
        'get',
        'getAll'
      ]
    }]],
  api: {
    baseURL: 'http://localhost:3000',
    browserBaseURL: 'http://localhost:3000'
  },
  md: {
    extend (config) {
      config.highlight = (code, lang) => {
        return `<pre class="language-${lang}"><code class="language-${lang}">${Prism.highlight(code, Prism.languages[lang], Prism.languages[lang])}</code></pre>`
      }
    }
  }
}

I've added the nuxtent module in my nuxt.config.js, and that is where I also load the prism CSS with:

  css: [
    'prismjs/themes/prism-okaidia.css'
  ]

What is expected ?

The markdown parser to properly extend the highlight option to use Prism js to highlihgt my

What is actually happening?

All of the 'pre' syntax highlighting loads from the css for the theme, rendering the text white with a shadow. However the rendered html does not have any of span tags parsed by Prism, and pre tag does not have the class applied either. Effectively, There is no difference in the page whether I extend the markdown parser or not.

When using a version of @nuxtjs/axios versions higher than 4.5.2 for example version 5.0.0 my get requests breaks with.

Error: Request failed with status code 404

Anyone with the same problem?

Cheers

{{ post.date }} grabs the date used in your file name. E.g. 2017-08-01-MyPost.vue would grab 2017-08-01 as the date.

Dated post are sorted by newest-oldest by default.

But yes you can sort them inside vue components. For example:

async asyncData({ app }) {
  return {
    posts: (await app.$content('/').getAll()).sort((page1, page2) => page2.date - page1.date)
  }
}

Closing this for now but let me know if that doesn't answers your question!