v1.9.0 had a breaking change #80
Comments
ljharb
added a commit
to ljharb/prop-types-tools
that referenced
this issue
Apr 21, 2020
- note: `install-peerdeps` is pinned to `~1.9` for now, due to nathanhleung/install-peerdeps#80
ljharb
added a commit
to enzymejs/enzyme
that referenced
this issue
Apr 21, 2020
ljharb
added a commit
to enzymejs/enzyme
that referenced
this issue
Apr 21, 2020
- [Fix] pin `install-peerdeps` to `~1.8`, due to nathanhleung/install-peerdeps#80 - [meta] Replace airbnb.io with enzymejs.github.io; update repo URLs - [dev deps] update `eslint`, `eslint-config-airbnb`, `eslint-plugin-react`, `eslint-plugin-react-hooks`, `eslint-plugin-import`, `in-publish`, `rimraf` - [Tests] [Dev Deps] Update to babel 7, use `babel-eslint`
|
Sorry about this, I didn't realize. Is there any solution other than to use a lower version of |
|
I'm not really sure. Based on some of the newer PRs, shelling out to npm is a better solution than using a proxy option anyways - if #85 lands, that might restore old node support by removing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
By adding
https-proxy-agentas a dep in ddf708b and 8579b31 - which requires node 4 - v1.9+ of install-peerdeps (whichenzyme-adapter-react-helperuses) stopped working in node < 4 (i use it in node 0.10 and 0.12)It would be great if a backport of v1 could be landed that fixes this, so I don't have to pin enzyme to v1.8 forever :-/ (see https://travis-ci.org/github/airbnb/prop-types/jobs/677498727 for the particular failure)
The text was updated successfully, but these errors were encountered: