I saw that when using https://nuxtjs.cmty.io/issues/new, my issue does NOT land here!
Instead it is landed here: https://cmty.app/nuxt/nuxtjs.org/issues/c143

This is very inconvenient and I hate having yet another app to get access to the issues.
What is the real tracker now then?

When joining gitter, you are redirected to discord.

HI, in my app,im run "npm run generate",but no html in my dist,and im try so many times，but here is no html。

help ！！ ！

What problem does this feature solve?

Currently, Nuxt.js document describes how to configure CSP, but there is no detailed setup method. I do not even know much about the existence of this feature.

What does the proposed changes look like?

Please tell me how to set up CSP in detail.

Implemented in https://github.com/nuxt/nuxtjs.org/commit/8098452dc1d3a34679edff37c68741cbb12f9a94

Implemented in https://github.com/nuxt/docs/commit/548c9bb11c6cf38d8acb430f8127552ceec180f3

I'm using UUID's in my URLS like so:

    validate({params}) {
      return params.id.match(/[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}/)
    },

I looked into it, and sadly, this seems like headache because they use an iframe an some weird links. You can use Chrome and right click -> Translate to XXX.

You're right, there isn't much documentation about this file or how the site is hosted/deployed.

The now.json file is used by the Now service. It makes it simple to deploy apps.

It's now fixed, thanks @Vuchan

Thank you for the suggestion :)

Hi, nuxt generate and then publish /dist to S3.
It work fine as I visit mydomain.com and go to mydomain.com/about(use nuxt-link).
But if I refresh in mydomain.com/about , S3 return "file does not appear" because mydomain.com/about/index.html only can.

I just know that i can conf many cdn to map all routes（use Error pages to return index.html）
So If any other solution？And how nuxtjs.org do?
Thanks.

First I want to say I'm super impressed with how routing gets handled in Nuxt. It is a huge productivity boost. One of the things I see confusing people, including me, is the flexibility of styles it allows/supports isn't as clear as it could be in the documentation. I've found there are two 'styles' that can be implemented.

One way is how the documentation site follows along:

foo/
_slug.vue
foo.vue

Another way is to put everything in the folder:

foo/
_slug.vue
index.vue
_param_id
index.vue
..etc…

I'm happy to add this in the documentation if a PR is an option.

Version

1.0

Reproduction link

https://nuxtjs.org/guide/plugins

Steps to reproduce

• After the plugin link is opened, please scroll to bottom of the page as a reader would do while going through the documentation
• Click on any other sidebar topic (say Modules)

What is expected ?

As a reader, when the topic (Plugins in this case) is completed, it is expected that they would select next (or any other topic). When the next topic is selected, they should be taken to the top of the page so that they can start reading from beginning.

What is actually happening?

When any topic link from sidebar is clicked, they are taken to the bottom of the page. The subtopic selected is the last one.

Additional comments?

I am fairly new to Nuxt, but may be adding scrollToTop() can help?

I'd like to ask that how to read the word nuxt? Is the 'u' read as vue's 'ue'?

带下划线404
Request URL: https://iambtr.github.io/_nuxt/style.css
Request Method: GET
Status Code: 404
不带下划线正常
Request URL: https://iambtr.github.io/nuxtjs/nuxt/style.css
Request Method: GET
Status Code: 200
怎么配置生成的_nuxt文件夹为 nuxt