Skip to content

Upgrade all deps#300

Merged
andywer merged 5 commits intoandywer:release-2.0from
vlad-zhukov:upgrade-deps
Oct 18, 2018
Merged

Upgrade all deps#300
andywer merged 5 commits intoandywer:release-2.0from
vlad-zhukov:upgrade-deps

Conversation

@vlad-zhukov
Copy link
Collaborator

No description provided.

const { css } = require('@webpack-blocks/assets')
const path = require('path')
const precss = require('precss')
const postcssVars = require('postcss-simple-vars')
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

precss is outdated and brings lots of dependencies with itself, but its features are not required for these tests.

@vlad-zhukov
Copy link
Collaborator Author

Ava fails with a weird babel error:
Error: You gave us a visitor for the node type TSUnknownKeyword but it's not a valid type

I can also reproduce it locally on release-2.0 branch, but CI doesn't...

@vlad-zhukov
Copy link
Collaborator Author

I guess the ava upgrade from my last PR didn't go well, downgrading the version works however.

andywer
andywer previously approved these changes Sep 30, 2018
Copy link
Owner

@andywer andywer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me 👌

Does someone else wanna have a look at the PR? 😉

@andywer
Copy link
Owner

andywer commented Sep 30, 2018

PS: Downgrading AVA seems fine.

@vlad-zhukov
Copy link
Collaborator Author

vlad-zhukov commented Oct 4, 2018

To sum up: if you update from one of previous commits to abb2d05 Upgrade root deps (#299) and run yarn, the yarn ava will run just fine. But on a fresh node_modules install this command will fail due to a weird error in one of Babel plugins ava uses.

I've downgraded ava from 1.0.0-beta.8 to 1.0.0-beta.7, updated almost all other deps and made sure the fresh install passes all tests. Everything should be fine now! 🙏

@andywer
Copy link
Owner

andywer commented Oct 4, 2018

Sounds good! Build is failing, though 🙃

We either need to find that dependency that's not compatible to node 6 or bump to minimum node 8. I would prefer continued support for node 6 if it's not too much effort.

@vlad-zhukov
Copy link
Collaborator Author

vlad-zhukov commented Oct 4, 2018

Damn, jsdom v12 dropped support for node 6, downgraded it back to v11.

@vlad-zhukov
Copy link
Collaborator Author

@andywer yeah, we should stick to what node version webpack supports, it's currently >=6.11.5

"preserveConstEnums": true,
"sourceMap": true,
"target": "es5",
"target": "es2015",
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The newest @types/node require it. Node 6 supports ES6, so it's fine.

@vlad-zhukov vlad-zhukov changed the title Upgrade a few deps Upgrade all deps Oct 10, 2018
andywer
andywer previously approved these changes Oct 18, 2018
@andywer andywer merged commit 44f85cf into andywer:release-2.0 Oct 18, 2018
@vlad-zhukov vlad-zhukov deleted the upgrade-deps branch October 18, 2018 17:01
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

Successfully merging this pull request may close these issues.

2 participants