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

Updated peerDependency to account for styled-components v4. #184

Conversation

alansouzati
Copy link

Also updated babel config to use env preset to avoid warning in the console when using the deprecated es2015 preset.

@alansouzati
Copy link
Author

something weird happened on the travis side. I don't think this is related to my changes.

Copy link
Member

@MicheleBertoli MicheleBertoli left a comment

Choose a reason for hiding this comment

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

Thanks for working on this, @alansouzati.
I added a couple of comments.

@@ -1 +1,2 @@
node_modules
package-lock.json
Copy link
Member

Choose a reason for hiding this comment

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

This shouldn't be needed, as there's no package-lock.json in this repo.

Copy link
Author

Choose a reason for hiding this comment

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

the problem is when I run npm install it gets added.

Copy link
Author

Choose a reason for hiding this comment

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

I think your recommendation is always to use yarn install since you are providing the yarn.lock file. sorry I missed that.

Copy link
Member

Choose a reason for hiding this comment

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

Yes, that would be the best given we have a yarn.lock.

@@ -58,7 +56,7 @@
"css": "^2.2.4"
},
"peerDependencies": {
"styled-components": "^2.0.0 || ^3.0.2"
"styled-components": "^2.0.0 || ^3.0.2 || >= 4.x"
Copy link
Member

Choose a reason for hiding this comment

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

Using babel-preset-env is OK, but this library is not ready yet for supporting v4.

Copy link
Author

Choose a reason for hiding this comment

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

I see. I'm not using enzyme, it is working with react-test-renderer. But I understand why you want to wait on adding that as a peerDependency.

Copy link
Member

Choose a reason for hiding this comment

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

Correct.
I was thinking about deprecate Enzyme, but I believe a lot of people find it useful.

@cellog cellog mentioned this pull request Jan 2, 2019
@spawnia
Copy link

spawnia commented Jan 28, 2019

@MicheleBertoli what is the status on this? Would really appreciate an update :)

@beausmith
Copy link

Ditto what @spawnia asked. When will this support styled-components@v4?

What needs to be done before this PR can be merged?

@MicheleBertoli Can you add a list of tasks to be completed before this PR is mergeable?

FYI - I'm using this with react-testing-library instead of Enzyme or react-test-renderer.

@shihlinlu
Copy link

I second @beausmith and @spawnia's comments. I don't think this library will be useful without supporting ^4.0+

@felipeleusin
Copy link

I think releasing a new major version that doesn't officially support enzyme while we get over those issues would be a good idea. Then we can do a quick release with the fixes.

This library works fine with react-testing-library and styled-components v4

@marlonmleite
Copy link

@MicheleBertoli what is the status on this? I'm working with mount of enzyme for write my tests with success. With this PR, I can rewrite using shallow.

@quantizor
Copy link
Contributor

No longer needed after general repo maintenance earlier today, thanks for your PR though! Just waiting to get added as an owner on npm so I can actually publish an update.

@quantizor quantizor closed this Jun 12, 2019
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.

None yet

8 participants