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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

After update microVM official template Vue + Vite stop working #8298

Open
3 tasks done
wkra opened this issue Jan 28, 2024 · 14 comments
Open
3 tasks done

After update microVM official template Vue + Vite stop working #8298

wkra opened this issue Jan 28, 2024 · 14 comments

Comments

@wkra
Copy link

wkra commented Jan 28, 2024

馃悰 bug report

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project
    adheres to.
  • I have searched the issue tracker for an issue that matches the one I want
    to file, without success.

Description of the problem

After update microVM official template Vue + Vite stop working

How has this issue affected you? What are you trying to accomplish?

There is no more possibility to use devbox environment after microVM update

To Reproduce

  • create Devbox with official Vue Vite template
  • click button "Update to latest microVM"
  • error [plugin:vite:vue] @vnode-* hooks in templates are no longer supported. Use the vue: prefix instead. For example, @vnode-mounted should be changed to @vue:mounted. @vnode-* hooks support has been removed in 3.4. appears

Link to sandbox: link (optional)

Your Environment

Software Name/Version
小odesandbox
Browser
Operating System
@CompuIves
Copy link
Member

Hello! Could you share the original template you forked from? I tried just with the "Vue (Vite)" template but I couldn't repro the issue. It's an interesting issue, from what I can gather the code for the example is outdated in comparison to the dependencies.

@wkra
Copy link
Author

wkra commented Jan 29, 2024

Hi :)
I have selected a template from the screen:
Capture73
Then I clicked the "Update to latest microVM button" in the top left corner.
Capture74
And without any changes to the code, errors appear:
Capture75
I tried to solve this somehow, but unfortunately without success. Link to the devbox from sceens: https://codesandbox.io/p/devbox/young-sky-76d998

@bogdan0083
Copy link

bogdan0083 commented Feb 13, 2024

I have the same problem after updating microVM. Restarting the task and refreshing browser doesn't help:

小薪懈屑芯泻 褝泻褉邪薪邪 2024-02-13 胁 21 22 19

Before updating, template was working just fine.

Update: Just tried to update all the dev dependencies to the latest version. Now the error is gone. Works fine.

@JamesACS
Copy link
Contributor

Thank you for confirming @bogdan0083 - The template isn't throwing these errors for us now even on load!

@CompuIves
Copy link
Member

Is this still an issue? We now have health checks on all our templates to ensure that nothing breaks again.

@bogdan0083
Copy link

bogdan0083 commented Mar 28, 2024

Is this still an issue? We now have health checks on all our templates to ensure that nothing breaks again.

Yep. The error is still present:

[plugin:vite:vue] @vnode-* hooks in templates are no longer supported. Use the vue: prefix instead. For example, @vnode-mounted should be changed to @vue:mounted. @vnode-* hooks support has been removed in 3.4.

Here's a newly created reproduction link: https://codesandbox.io/p/devbox/awesome-nash-k7rtks?file=%2Fpackage.json%3A12%2C20

If the error is not showing try to terminate vite server and run npm run dev.

小薪懈屑芯泻 褝泻褉邪薪邪 2024-03-28 胁 21 58 47

@JamesACS
Copy link
Contributor

Hello @bogdan0083

I've just tried to replicate this and restarting the environment seems to resolve the issue.

Please could you confirm this?

@bogdan0083
Copy link

bogdan0083 commented Mar 29, 2024

Hello @bogdan0083

I've just tried to replicate this and restarting the environment seems to resolve the issue.

Please could you confirm this?

Hmm, you're right. Clicking "Restart Devbox" actually resolves the issue. Thanks!

@dgonzalezr
Copy link

dgonzalezr commented Apr 1, 2024

Hi there 馃憢馃徏

I'm still getting this problem, and I can confirm it only happens on Codesandbox (devbox) because I was able to download the Devbox and run it without issues locally. Restarting the environment did not solve anything for me.

CleanShot 2024-04-02 at 15 01 08@2x

Here's the reproduction link: https://codesandbox.io/p/devbox/beeq-vuejs3-2d8p9t

@filipelima18
Copy link
Contributor

Hi @dgonzalezr! I forked your Devbox just now and then manually restarted the Devbox, and the preview works as expected. You can check my forked Devbox here.

Here's the option I used to restart the Devbox:
image

Can you try again and confirm if it's working?

@mho22
Copy link

mho22 commented Apr 17, 2024

I also get this issue here. Creating a public devbox returns the error with Vue + Vite

The idea is to display some code and views to people who don't have an account on codesandbox. [ In my case : People going on my website are being redirected on Codesandbox. ] If they want to play with code they have to create an account. But with this displayed error, nobody will be tempted to create an account.

The restart devbox option isn't available for guests. There's no tool to restart the devbox here.

@filipelima18
Copy link
Contributor

Hi @mho22. Are you embedding a public Devbox you created? If so, you should be able to restart the Devbox yourself so that it solves the error for guests.

@mho22
Copy link

mho22 commented Apr 23, 2024

@filipelima18 Hi @filipelima18, I am using the githubbox url method to share my github project on codesandbox. Should I create a public Devbox from my own repo instead ?

@dgonzalezr
Copy link

dgonzalezr commented May 16, 2024

Hi there @filipelima18

The issue is happening again: https://codesandbox.io/p/devbox/beeq-with-vuejs-forked-4l26fc?file=%2Fsrc%2Fviews%2FAbout.vue

CleanShot 2024-05-16 at 12 37 00@2x

Forking and restarting manually the DevBox makes no difference, the error is still there! 馃槙

Late Edit: I've managed to make it work again, but still quite annoying that this issue could appear any time.

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

7 participants