Activities

khrome83

khrome83 posted a new bug report

docs •

bug TypeScript setup broken in newest version

Version

2.5.x

Reproduction link

https://nuxtjs.org/guide/typescript/

Steps to reproduce

Follow Installation Guide Here - https://nuxtjs.org/guide/typescript/

What is expected ?

TypeScript works as expected…

What is actually happening?

The pages/feed.vue file throws a TypeScript error.
Screen Shot 2019-04-17 at 6.51.05 AM.png

Additional comments?

The code is copied and pasted exactly. After tons of research, I can't find a workaround with the exception of setting up *.d.ts files and overriding the behavior or turning off StrictFunctions. I am new to typescript​ and was really relying on this guide to integrate with it.

sebas1208

sebas1208 posted a new question

docs •

Translation to Spanish

Hello Nuxt Team. I want to say thanks for your amazing job.

I want to know if there is an active development for translation to Spanish? I see that there were some efforts to do this before, what is the current state of this? I'd like to help if you agree, but I don't know where to start.

sebas1208

sebas1208 posted a new question

docs •

Translation to Spanish

Hello Nuxt Team. I want to say thanks for your amazing job.

I want to know if there is an active development for translation to Spanish? I see that there were some efforts to do this before, what is the current state of this? I'd like to help if you agree, but I don't know where to start.

pablocattaneo

pablocattaneo posted a new bug report

docs •

bug Faq page only show How to use external resources

Reproduction link

https://nuxtjs.org/faq

Steps to reproduce

Go into https://nuxtjs.org/faq

What is expected ?

See all this content:

https://github.com/nuxt/docs/tree/master/en/faq

What is actually happening?

The only content show in https://nuxtjs.org/faq is https://github.com/nuxt/docs/blob/master/en/faq/external-resources.md
CopyQ.kn1412.png

chenhongjian37

chenhongjian37 posted a new question

docs •

Custom layout uses official routing animation without effect.

I used a custom layout on the page: layout:'empty', when I wanted to use animation alone on the page, it still had no effect. If I use the official default layout "default", I can achieve the effect. Global animation is possible, but some of the animations on the page are not.

chenhongjian37

chenhongjian37 posted a new question

docs •

自定义layout 使用官方的路由动画无效果
JohnTitor

JohnTitor posted a new bug report

docs •

bug ja: some words aren't italic

Version

2.3.X

Reproduction link

https://ja.nuxtjs.org/faq/netlify-deployment/

Steps to reproduce

See https://ja.nuxtjs.org/faq/netlify-deployment/

What is expected ?

Specific words are italic correctly.

DeepinScreenshot_select-area_20190325020904.png

What is actually happening?

Some words aren't italic, e.g. *"New site from Git"*

DeepinScreenshot_select-area_20190325020852.png

Additional comments?

This will be fixed by using underscores like the other languages' documentation but it seems that asterisks are used in Japanese documentation. If the work is just to replace * with _, I can open a PR.

nelsonlarocca

nelsonlarocca posted a new question

docs •

getters don't return updated values

I have a store

  • store
    --- index.js
    --- biz
    ----- index.js

// store/index.js
const actions = {
nuxtServerInit({ dispatch }, context) {
return Promise.all([dispatch('biz/nuxtServerInit', context)])
}
}

export default {
namespaced: true,
actions
}

//biz/index.js
const state = () => ({
name: null,
id: null
})

// -
// - MUTATIONS -
// -
const mutations = {
mutInitBiz(state, obj) {
aPromise(obj).then(x => {
state.name = x.name
state.id = x.id
console.log('bizName ==> ', state.name) // these two values are displayed
console.log('bizId ===> ', state.id) // with the updated values
})
}
}

// -
// - ACTIONS -
// -
const actions = {
nuxtServerInit(vuexContext, context) {

vuexContext.commit(
  'mutInitBiz',
  'someData'
)

}
}
// -
// - GETTERS -
// -
const getters = {
name: state => {
return state.name // always returns null (the initial value)
},
id() {
console.log('GETTER BIZ ID', state.id) // always returns null (the initial value)
},
return state['biz/bizId']
},
}

export default {
namespaced: true,
state,
actions,
mutations,
getters
}

within the mutation the console drops the right values, but the getters don't get the updated ones but just the initial ones. What do you think guys I could be missing ?

cfjedimaster

cfjedimaster posted a new bug report

docs •

bug Documentation confusion for generate

Version

2.4.5

Reproduction link

https://nuxtjs.org/guide/commands

Steps to reproduce

(This is a copy and paste from a previous bug posted on the wrong repo.)
The docs say this about generate and dynamic routes:

"If you have a project with dynamic routes, take a look at the generate configuration to tell Nuxt.js how to generate these dynamic routes."

The link there goes to here: https://nuxtjs.org/api/configuration-generate. And that page says, very clearly:

"Dynamic routes are ignored by the generate command."

However when I tested a simple app with dynamic routes, the generate command created a SPA that worked perfectly. I did some Googling and found this Reddit post mentioning the same behavior:

https://www.reddit.com/r/Nuxt/comments/9wy72h/i_can_still_access_dynamic_route_params_with_nuxt/

So I guess my question/issue is: Is this expected, and if so, shouldn't the docs make it clear? Btw I'd be happy to help write those docs, but I just wanted to be sure.

As a followup, if the generate command is seeing the dynamic routes and auto creating a SPA, does this mean I can't not create a SPA? Like if I set up a generate config and want a non-SPA static app, will I be able to if the generate command seems to force it anyway?

What is expected ?

The docs should explain the behavior a bit more.

What is actually happening?

They don't. :)

adabutch

adabutch posted a new question

docs •

Google Analytics - "Full view mode" vs "Embedded mode"

After installing GA via a plugin, I never saw any traffic being picked up in my GA dashboard despite seeing success in my network inspector, etc. I made the change outlined by @oliver3 here and now things are working as desired.

My question is, if it's worth adding to the documentation that this change is necessary? Assuming other folks have also gotten tripped up.

Thanks for the consideration!

DFASD

DFASD posted a new question

docs •

使用nuxt generate 命令静态渲染之后,将dist目录下的文件部署上线网站访问特别慢!不知道什么原因!就一个banner图片和logo都是本地资源!
SumNeuron

SumNeuron posted a new question

docs •

Documentation Request vuex-store.md

The vuex store documentation needs to be extended to give more clear specification on more complex store structures.

e.g.

store/
--state.js
--actions.js
--getters.js
--mutations.js
--index.js
--modules/
--+--moduleA/
--+--+--state.js
--+--+--actions.js
--+--+--getters.js
--+--+--mutations.js
--+--+--index.js
--+--moduleB/
--+--+--state.js
--+--+--actions.js
--+--+--getters.js
--+--+--mutations.js
--+--+--index.js

currently as it stands it states:

You can optionally break down a module file into separate files: state.js, actions.js, mutations.js and getters.js. If you maintain an index.js file with state, getters and mutations while having a single separate file for actions, that will also still be properly recognized.

which is fine if your store has no modules.
but it doesnt clarify how to arrange this for multiple modules.

In addition, for the "classic mode" which will be deprecate in v3

there is no documentation for what the index file should be:

here is an example from my project

import Vuex from 'vuex'

import mutations from '@/store/mutations.js';
import actions from '@/store/actions.js';
import getters from '@/store/getters.js';
import state from '@/store/state.js';

const createStore = () => {
  const store = new Vuex.Store({
    namespaced: true,
    state,
    actions,
    getters,
    mutations,
    modules: {}
  })

  return store
}

export default createStore

so all this information should be provided

laitang2000

laitang2000 posted a new question

docs •

Nuxt-ts documentation clarification

The documentation isn't clear about the process of using Nuxt-ts and it would be helpful if you guys can clarify some points I have.

Is Nuxt-ts to be used interdependently of Nuxt i.e. should there only be either Nuxt or Nuxt-ts in the packages.json

When adding Nuxt-ts to an existing project via yarn or npm do I have to create a tsconfig.json?

Is intellisense possible in the the template markup of a component when using Nuxt-ts?

Thanks in advance

laitang2000

laitang2000 posted a new question

docs •

Nuxt-ts adding to existing nuxt project

The documentation isn't clear about the process of using Nuxt-ts and it would be helpful if you guys can clarify some points I have.

Is Nuxt-ts to be used interdependently of Nuxt i.e. should there only be either Nuxt or Nuxt-ts in the packages.json

When adding Nuxt-ts to an existing project via yarn or npm do I have to create a tsconfig.json?

Is intellisense possible in the the template markup of a component when using Nuxt-ts?

Thanks in advance

maluio

maluio posted a new feature request

docs •

idea Event handling / component communication

What problem does this feature solve?

My use case was:
A button in a parent component triggers a method call in a child component.

I couldn't find a solution in the nuxtjs docs. Eventually, I stumbled upon this thread:
https://github.com/nuxt/nuxt.js/issues/849

Using

this.$root.$emit
this.$root.$on

solved my problem.

What does the proposed changes look like?

Ideally, a new page explains the available options for component communication: (this.$root.$emit, eventBus, …)

The new page could be available at https://nuxtjs.org/api/component-communiction

If this is a valid feature request I could write that page.

Thank you.

otofune

otofune resolved the question #c166

docs •

please ignore this issue

Just close it.

otofune

otofune resolved the question #c175

docs •

please ignore this issue

Just close it.

otofune

otofune resolved the question #c176

docs •

please ignore this issue

Just close it.

otofune

otofune resolved the question #c177

docs •

please ignore this issue

Just close it.

otofune

otofune resolved the question #c173

docs •

please ignore this issue

Just close it.