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

bump @blueprintjs dependencies #1038

Merged
merged 1 commit into from
Nov 13, 2019
Merged

bump @blueprintjs dependencies #1038

merged 1 commit into from
Nov 13, 2019

Conversation

seve
Copy link
Contributor

@seve seve commented Nov 13, 2019

This PR bumps all of our BlueprintJS dependencies as follows:

  • @blueprintjs/core 3.18.1 -> 3.20.0
  • @blueprintjs/icons 3.10.0 -> 3.12.0
  • @blueprintjs/select 3.10.0 -> 3.11.2

This fix eliminates console warnings from using renamed/deprecated lifecycle methods.

Note that the following error is still present:

Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: SideEffect(NullComponent)

Closes #926

@seve seve merged commit 68ad4b1 into master Nov 13, 2019
@colinmegill colinmegill deleted the seve/bump-blueprint-version branch November 13, 2019 20:04
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.

react console warning on master
2 participants