What problem does this feature solve?

Developer experience, also might reduce the number of issues reported if devs knew how to step through the code when required.

What does the proposed changes look like?

Add simple debugging examples using

VS Code
WebStorm
Chrome

I get bad news where the url https://player.vimeo.com/video/311756540 with the vimeo.com domain has been blocked.
This blocking applies in the country of Indonesia, it is blocked based on expressions from Kominfo Indonesia for vimeo.com. So, this blocking makes the video blank.

I hope YouTube is much better, Vue Mastery video

Thanks
@debs-obrien

Version

v1.1.0

Reproduction link

nuxtjs.org/blog

Steps to reproduce

1. Go to nuxtjs.org/blog
2. Open any blog post with cmd + mouse click (Mac) or ctrl + mouse click (Windows).
3. Link opens in a new tab but also navigates to the article. Now 2 same articles are open.

What is expected ?

When using cmd / ctrl with mouse click a link should open ONLY in new tab without affecting current page.

What is actually happening?

cmd / ctrl with mouse click opens blog article twice.

Additional comments?

• It seems that this problem exists only on /blog page.
• Clicking an article link with mouse wheel (middle click) works fine.

What problem does this feature solve?

In dark mode, it was hard to see an exit button when an image was full screen. I also think it is more intuitive to have to @click close when you click either the image or exit button, but that's personal opinion.

What does the proposed changes look like?

I am making a PR.

Pull Request #412

Hey all 👋

at the moment, the terms Nuxt.js, Nuxt and NuxtJS are not used consistently, nor they are "explained" somewhere.

From my current understanding, these terms are used like that:

• The framework = Nuxt.js
• The company = NuxtJS
• "Colloqiually" referrencing to the Framework and ecosystem (should be avoided) = Nuxt

Questions

1. Is this still correct?
2. Because many people (still) think that NuxtJS === Nuxt.js, could we somewhere explain the terms correctly?
3. Would you accept PRs to fix the terminology in case 1. is answered with "yes"?

Checking with latest version:

• build.vendor is not effective since nuxt 2.0 (module contamination creates vendor and shared chunks automatically)
• "modules served thought npm packages and also be accessed via plugins" --> This is totally wrong because modules and plugins are not ina same context but can also provide plugins. Wording could be like services added by other plugins using $inject or so?

Some suggestions

• Maybe would be better advising plugin.client.js (and also .server.js) instead of { ssr: false }
• It would be probably better to use export default for nuxt.config (and removing .js to simplify and typescript users)
• Maybe nice including buildModules

Checking latest version of context, these are not part of real nuxt context: env and isDev are not part of nuxt context object but provided by webpack during build by usage for process.*. Maybe would be better to remove them to avoid misunderstanding or add a notice?

Raw assets for diagrams is not published (or probably I'm missing). By publishing, contributors can modify them to update the docs. Ideally, we may also automate static assets generation from the source.

Checking guides directory, we are currently using jpeg and png for diagrams. Jpeg compression is always lossy and for png files are also using lossy compression format which decreases text readability and makes size bigger. I would recommend using SVG format as even internet explorer supports it.

Version

v1.1.0

Reproduction link

https://nuxtjs.org/

Steps to reproduce

1. Press "/" to focus search field
2. Enter some text (for example, I searched for "async"
3. Press enter to search, or try to press the search icon

What is expected ?

Search results are shown

What is actually happening?

Nothing happens. No errors in console either

What problem does this feature solve?

People (like myself) can't use Nuxt to render docs from markdown files on GitHub, without having to do all the scaffolding manually, or copying and pasting code from the nextjs.org repo. Additionally, having this functionality used independently should hopefully result in a more accessible contributor ecosystem meaning the docs module is more likely to have community contributed bugfixes and enhancements.

What does the proposed changes look like?

Hopefully not much more than:

• Allowing the source of the docs to be configured (https://github.com/nuxt/nuxtjs.org/blob/master/modules/docs/server.js#L93)
• moving the modules/docs folder to it's own repo
• adding a new package on NPM
• adjusting the integration within the nuxtjs.org repo

like this :
_id1.vue
_id2.vue

i upgrade nuxtjs 2.12 to 2.13 and run my project failed nuxtjs say to

\template\nuxt\config.json: isFullStatic is not defined

Version

2.12.x

Reproduction link

https://nuxtjs.org/guide/installation

Steps to reproduce

Page worked a few minutes ago, now is down. Checked multiple browsers and asked coworkers to also check, all see the same.

What is expected ?

Should have install instructions

What is actually happening?

Blank page

Additional comments?

was trying to follow instructions and they vanished

tis is my store :
export const state = () => ({
products: [],
categories: [],
subCategories: []
});

export const getters = {
getProducts(state) {
return state.products;
},
getCategories(state) {
return state.categories;
},
getSubCategories(state) {
return state.subCategories;
}
};
export const mutations = {
SETPRODUCTS(state, payload) { state.products = payload; }, SETCATEGORIES(state, payload) {
state.categories = payload;
},
SET_SUBCATEGORIES(state, payload) {
state.subCategories = payload;
}
};

export const actions = {
async productsAPI({ commit }) {
const { data } = await this.$axios.get("http://localhost:8080/products");
commit("SETPRODUCTS", data); }, async categoriesAPI({ commit }) { const categories = await this.$axios.$get( "http://localhost:8080/categories" ); commit("SETCATEGORIES", data);
},
async subCategoriesAPI({ commit }) {
const subcategories = await this.$axios.$get(
"http://localhost:8080/subcategories"
);
commit("SET_SUBCATEGORIES", data);
}
};