-
Notifications
You must be signed in to change notification settings - Fork 14
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
fix: downgrades to vue 2.6.12 #162
Conversation
Styleguide deployed to https://square.github.io/maker/styleguide/revert-to-vue-2.6.12/#/ |
📊 Package size report 1%↑
Unchanged files
Hidden files
🤖 This report was automatically generated by pkg-size-action |
It's because the previous version of Vue isn't compatible with Webpack 5: vuejs/vue#12002 Anyway, downgrading and sticking to a lower version of Vue.js isn't a long-term solution. We should investigate the root cause in the latest version of Vue.js 2. Have you tried upgrading Website to 2.6.14? |
but building the components with vue 2.6.12 and webpack 5.58.0 seems to work just fine, and building the lab and styleguide with those package versions also seems to work just fine, e.g. the deployed styleguide: https://square.github.io/maker/styleguide/revert-to-vue-2.6.12/#/ the only thing that fails for some weird reason is local doc dev with
No because that would be impossible to fully QA, it's much easier, simpler, faster, and safer to just downgrade Maker to vue 2.6.12 (at least for the time being). |
vuejs/vue#12002 is a SSR fix, and local dev uses SSR but building to GitHub Pages doesn't. Let's investigate the root cause first. |
When you say "investigate the root cause" do you mean looking into why vue components built using vue v2.6.14 do not work as expected when imported and rendered in another project using vue v2.6.12? We know the specific component that breaks is MContainer, and the specific way it breaks is that props which are used as the default/fallback content for slots no longer render, and those slots are wrapped with v-ifs: https://github.com/square/maker/blob/master/src/components/Container/src/Container.vue#L12-L39 After looking at the vue v2.6.13 and v2.6.14 release notes this particular PR really stands out, and is likely the source of the introduced breaking behavior: vuejs/vue#12104 Although we have yet to confirm that's the cause, if we assume that it is... then what do we do? |
I've tried upgrading Website to Vue 2.6.14 and it also fixed the issue, so our options are:
|
Yes, the consumer must use 2.6.14 too. This regression will not be fixed on Vue's end: vuejs/vue#12314 Upgrade is inevitable so let's upgrade Website and file a Q&A request. |
closing this as we're just gonna bump Website to vue 2.6.14 instead, and if that doesn't work we'll get rid of the props from MContainer and leave only slots. |
Describe the problem this PR addresses
JIRA: https://jira.sqprod.co/browse/WEBSITE-1244
MContainer's label, sublabel, and requirement-label props do not work within the Website codebase, I think this might have something to do with Website being on vue (and vue-template-compiler) v2.6.12 while Maker uses vue (and vue-template-compiler) v2.6.14 so this is a test branch where i downgrade Maker's vue & friends deps to 2.6.12 buuuut I'm running into some issues...
UPDATE: DOWNGRADING VUE TO v2.6.12 FIXED THE ISSUE (I have confirmed it locally by npm linking this branch into Website).
Describe the changes in this PR
downgrades vue & friends to 2.6.12
Other information
this branch breaks local doc dev -_-
when i attempt to run
component=Container npm run dev
I get the following error:screenshot:
![image](https://user-images.githubusercontent.com/7769424/136444894-99b0cfea-12ba-4dde-a812-603d5b7c54d3.png)
I don't understand why downgrading Vue a couple patch versions would cause this error, and I don't understand how I'm suppose to fix it... it seems like the fix may have to go into
vue-just-ssr
? cc @privatenumber