-
Notifications
You must be signed in to change notification settings - Fork 294
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
Nuxt Removal #5287
Nuxt Removal #5287
Conversation
17bd539
to
538b315
Compare
I'm working through errors in ci, but I still think this is in a state where it's ready to start reviewing |
cba2dc8
to
31ece93
Compare
The only failure at this point is spell check in files that got modified, but none of these typos are new.. I'll work on resolving those. |
After a
The I was able to do a This is all on Linux (openSUSE Leap 15.3). I will test on Windows shortly. |
This is an old issue that exists in our components that we import from Dashboard, so I don't think that's the problem. If you've run e2e tests recently on your workstation, you might want to make sure that there aren't any zombie nuxt processes hanging around, that could be the culprit. I've been developing primarily on openSUSE Tumbleweed, but I can spin up an openSUSE Leap 15.3 vm to see if there's any change in behavior there. |
Ok this is weird. The same thing is happening on windows 10: after a reboot and a |
@adamkpickering can you provide the output of |
Here is the full output:
|
Hold on, looks like it worked that time... |
I'm thinking there's something going on here, seeing as how you replicated in two different environments. I still need to provision a new vm to test , maybe that can shed some light. |
I now realize my previous comment wasn't completely accurate: I had run a
And RD failed to start with the following output:
Maybe the I then tried running
Finally I did the following procedure, to check whether
Lo and behold, it worked on step 4 with the following output:
And, I can't see any error messages in that last block of text. Maybe something is being built out of order? |
It does seem to be the case that something is being built out of order. You have the following line in your first example:
This is raised long before the frontend dev server is ready, so this is telling us that the backend is starting alongside the frontend. I saw something similar with e2e tests as well, but I'm mighty curious as to why our spawn wrapper is executing out of sequence. |
@adamkpickering I made some modifications to the dev script to
Can you test this and let me know if the change resolves your issue? |
c59a29a
to
e91c0f5
Compare
I tried it, and got a new error:
|
@adamkpickering okay, that's better.
This at least tells me that it's failing exactly where I originally thought that it would. I can try to tweak this so that we can delay the time that it takes to fail. |
@adamkpickering ready for another attempt when you're ready. |
85d4a3c
to
4f8ecb4
Compare
Invoke vue cli for build scripts Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Remove vue cli eslint plugin, as we should defer to linting via scripts defined in `package.json` Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Rename `startRendererProcess` to `buildRenderer` Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Fix lint errors Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
8d8b121
to
b1b4b49
Compare
Yeah, this error is directly related to merging #5258. This PR has been rebased and updated to accommodate the new Containers route. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything passed for me on all three platforms, and the current changeset looks fine.
This follows the same strategy implemented in rancher/dashboard#7211, where we take all of the nuxt generated files and move them into
pkg/rancher-desktop/nuxt
, and migratenuxt.config.js
tovue.config.js
.In addition to these changes, this PR also installs vue-cli and upgrades Vue to v2.7.14, the latest version of Vue available on the 2.x branch. Making this change allows us to target a single version of typescript (v4.5.6) and resolves any comparability issues that we might have previously encountered. Most notably, no more typescript warnings when installing dependencies.
Finally, the Vue upgrade also includes an update to webpack 5. This introduces some breaking changes, so we need to update our webpack configs to accommodate this.
closes #5000