Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug Report] VSkeletonLoader not showing in production #9865

Closed
SumNeuron opened this issue Dec 3, 2019 · 10 comments
Closed

[Bug Report] VSkeletonLoader not showing in production #9865

SumNeuron opened this issue Dec 3, 2019 · 10 comments

Comments

@SumNeuron
Copy link

SumNeuron commented Dec 3, 2019

Environment

Vuetify Version: 2.1.12
Vue Version: 2.6.10
Browsers: Firefox 71.0
OS: Linux x86_64

Steps to reproduce

NOTE: it is gitlab not github (changed to pass form validation)

  1. Clone repo
  2. use python docker script to build and launch dev environment python docker.py -c up
  3. go to localhost. You should see v-skeleton-loader of type table which comes from component VBoilerplate.vue (taken from Vuetify.js documentation)
  4. stop dev environment python docker.py -c down
  5. launch production environment python docker.py -c up -p
  6. go to localhost:3000, notice component is mounted, but skeleton loader is nowhere to be seen (you can also see the deployed gitlab page here: https://sumneuron.gitlab.io/vskel/ vue tools are enabled)

Expected Behavior

"It just works", no extra configuration between dev and production for vskeletonloader / vboilerplate

Actual Behavior

skeletonloader not shown in production

Reproduction Link

https://gitlab.com/SumNeuron/vskel

I hope dockerized git repo is ok

@ghost ghost added the S: triage label Dec 3, 2019
@jacekkarczmarczyk
Copy link
Member

image

@jacekkarczmarczyk jacekkarczmarczyk added the S: needs reproduction The issue does not contain a valid reproduction label Dec 4, 2019
@SumNeuron
Copy link
Author

@jacekkarczmarczyk as stated in comments it is a gitlab repository. The form only allowed gothub

@jacekkarczmarczyk jacekkarczmarczyk removed the S: needs reproduction The issue does not contain a valid reproduction label Dec 4, 2019
@jacekkarczmarczyk
Copy link
Member

OK, btw you can edit issue in github

@SumNeuron
Copy link
Author

@jacekkarczmarczyk I didn't know if that would cause issues since there is the form to populate it. Are you able to reproduce it at least?

@jacekkarczmarczyk
Copy link
Member

No, I don't use docker and I'm not familiar with nuxt, also I don't think it requires any of them to reproduce. Did you try to create a simple vue-cli reproduction?

@SumNeuron
Copy link
Author

Would you be willing to humor me then? You do not have to use docker. you can

npm run dev

and for production

npm build
npm run start

@SumNeuron
Copy link
Author

@jacekkarczmarczyk does that work for you? You don't need to be familiar with nuxt to see the issue

@jacekkarczmarczyk
Copy link
Member

jacekkarczmarczyk commented Dec 7, 2019

I can reproduce but it looks more like a nuxtjs or @nuxtjs/vuetify issue

@kevinmarrec
Copy link
Contributor

kevinmarrec commented Dec 9, 2019

Not a Nuxt.js or Vuetify issue, it's just Vue.js render function that doesn't support component names unless it is already registered globally. Component should directly be passed to the h instead.

See nuxt-community/vuetify-module#224 (comment) for in-depth explanations.

@KaelWD
Copy link
Member

KaelWD commented Dec 9, 2019

Yeah this is vuejs/vue#7492

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants