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

fix(deps): update all non-major dependencies #43

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 29, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
babel-plugin-import 1.13.3 -> 1.13.5 age adoption passing confidence
firebase (source, changelog) 9.0.1 -> 9.14.0 age adoption passing confidence
husky (source) 7.0.2 -> 7.0.4 age adoption passing confidence
lint-staged 11.1.2 -> 11.2.6 age adoption passing confidence
prettier (source) 2.3.2 -> 2.7.1 age adoption passing confidence
promise 8.1.0 -> 8.3.0 age adoption passing confidence
react-redux 7.2.5 -> 7.2.9 age adoption passing confidence
redux (source) 4.1.1 -> 4.2.0 age adoption passing confidence
redux-thunk 2.3.0 -> 2.4.2 age adoption passing confidence
serve 12.0.0 -> 12.0.1 age adoption passing confidence
styled-components (source) 5.3.1 -> 5.3.6 age adoption passing confidence
typescript (source) 4.4.2 -> 4.9.3 age adoption passing confidence

Release Notes

ant-design/babel-plugin-import

v1.13.5

Compare Source

v1.13.4

Compare Source

firebase/firebase-js-sdk

v9.14.0

Compare Source

v9.13.0

Compare Source

v9.12.1

Compare Source

v9.12.0

Compare Source

v9.11.0

Compare Source

v9.10.0

Compare Source

v9.9.4

Compare Source

v9.9.3

Compare Source

v9.9.0

Compare Source

v9.8.4

Compare Source

v9.8.3

Compare Source

v9.8.2

Compare Source

v9.8.1

Compare Source

v9.8.0

Compare Source

v9.7.0

Compare Source

v9.6.11

Compare Source

v9.6.10

Compare Source

v9.6.9

Compare Source

v9.6.8

Compare Source

v9.6.7

Compare Source

v9.6.6

Compare Source

v9.6.5

Compare Source

v9.6.4

Compare Source

v9.6.3

Compare Source

v9.6.2

Compare Source

v9.6.1

Compare Source

v9.6.0

Compare Source

v9.5.0

Compare Source

v9.4.1

Compare Source

v9.4.0

Compare Source

v9.3.0

Compare Source

v9.2.0

Compare Source

v9.1.3

Compare Source

v9.1.2

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

v9.0.2

Compare Source

typicode/husky

v7.0.4

Compare Source

No changes. Husky v7.0.3 was reverted, this version is the same as v7.0.2.

v7.0.3

Compare Source

okonet/lint-staged

v11.2.6

Compare Source

Bug Fixes

v11.2.5

Compare Source

Bug Fixes

v11.2.4

Compare Source

Performance Improvements

v11.2.3

Compare Source

Bug Fixes

v11.2.2

Compare Source

Bug Fixes

v11.2.1

Compare Source

Bug Fixes

v11.2.0

Compare Source

Features

v11.1.4

Compare Source

v11.1.3

Compare Source

prettier/prettier

v2.7.1

Compare Source

diff

Keep useful empty lines in description (#​13013 by @​chimurai)

v2.7.0

Compare Source

"""
First line
Second Line
"""
type Person {
name: String
}

v2.6.2

Compare Source

diff

Fix LESS/SCSS format error (#​12536 by @​fisker)
// Input
.background-gradient(@​cut) {
    background: linear-gradient(
        to right,
        @​white 0%,
        @​white (@​cut - 0.01%),
        @​portal-background @​cut,
        @​portal-background 100%
    );
}

// Prettier 2.6.1
TypeError: Cannot read properties of undefined (reading 'endOffset')

// Prettier 2.6.2
.background-gradient(@​cut) {
  background: linear-gradient(
    to right,
    @​white 0%,
    @​white (@​cut - 0.01%),
    @​portal-background @​cut,
    @​portal-background 100%
  );
}
Update meriyah to fix several bugs (#​12567 by @​fisker, fixes in meriyah by @​3cp)

Fixes bugs when parsing following valid code:

foo(await bar());
const regex = /.*/ms;
const element = <p>{/w/.test(s)}</p>;
class A extends B {
  #privateMethod() {
    super.method();
  }
}

v2.6.1

Compare Source

diff

Ignore loglevel when printing information (#​12477 by @​fisker)

v2.6.0

Compare Source

prettier --loglevel silent --find-config-path index.js

v2.5.1

Compare Source

diff

Improve formatting for empty tuple types (#​11884 by @​sosukesuzuki)
// Input
type Foo =
  Foooooooooooooooooooooooooooooooooooooooooooooooooooooooooo extends []
    ? Foo3
    : Foo4;

// Prettier 2.5.0
type Foo = Foooooooooooooooooooooooooooooooooooooooooooooooooooooooooo extends [

]
  ? Foo3
  : Foo4;

// Prettier 2.5.0 (tailingCommma = all)
// Invalid TypeScript code
type Foo = Foooooooooooooooooooooooooooooooooooooooooooooooooooooooooo extends [
  ,
]
  ? Foo3
  : Foo4;

// Prettier 2.5.1
type Foo =
  Foooooooooooooooooooooooooooooooooooooooooooooooooooooooooo extends []
    ? Foo3
    : Foo4;
Fix compatibility with Jest inline snapshot test (#​11892 by @​fisker)

A internal change in [email protected] accidentally breaks the Jest inline snapshot test.

Support Glimmer's named blocks (#​11899 by @​duailibe)

Prettier already supported this feature, but it converted empty named blocks to self-closing, which is not supported by the Glimmer compiler.

See: Glimmer's named blocks.

// Input
<Component>
  <:named></:named>
</Component>

// Prettier 2.5.0
<Component>
  <:named />
</Component>

// Prettier 2.5.1
<Component>
  <:named></:named>
</Component>

v2.5.0

Compare Source

diff

🔗 Release Notes

v2.4.1

Compare Source

diff

Fix wildcard syntax in @forward (#​11482) (#​11487 by @​niksy)
// Input
@&#8203;forward "library" as btn-*;

// Prettier 2.4.0
@&#8203;forward "library" as btn- *;

// Prettier 2.4.1
@&#8203;forward "library" as btn-*;
Add new CLI option debug-print-ast (#​11514 by @​sosukesuzuki)

A new --debug-print-ast CLI flag for debugging.

v2.4.0

Compare Source

diff

🔗 Release Notes

then/promise

v8.3.0

Compare Source

New Features

v8.2.0

Compare Source

New Features
  • Add support for Promise.allSettled (#​171)
reduxjs/react-redux

v7.2.9

Compare Source

This patch release updates the rarely-used areStatesEqual option for connect to now pass through ownProps for additional use in determining which pieces of state to compare if desired.

The new signature is:

{
  areStatesEqual?: (
    nextState: State,
    prevState: State,
    nextOwnProps: TOwnProps,
    prevOwnProps: TOwnProps
  ) => boolean
}

What's Changed

Full Changelog: reduxjs/react-redux@v7.2.8...v7.2.9

v7.2.8

Compare Source

This release fixes a bug in the 7.x branch that caused <Provider> to unsubscribe and stop updating completely when used inside of React 18's <StrictMode>. The new "strict effects" behavior double-mounts components, and the subscription needed to be set up inside of a useLayoutEffect instead of a useMemo. This was previously fixed as part of v8 development, and we've backported it.

Note: If you are now using React 18, we strongly recommend using the React-Redux v8 beta instead of v7.x!. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code.

Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. Per an update yesterday in the "v8 roadmap" thread, React-Redux v8 will be updated in the next couple days to ensure support for React 16.8+ as part of the next beta release. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version.

Full Changelog: reduxjs/react-redux@v7.2.7...v7.2.8

v7.2.7

Compare Source

This release updates React-Redux v7's peer dependencies to accept React 18 as a valid version, only to avoid installation errors caused by NPM's "install all the peer deps and error if they don't match" behavior.

Note: If you are now using React 18, we strongly recommend using the React-Redux v8 beta instead of v7.x!. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code.

Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version.

v7.2.6

Compare Source

Just a quick fix for a Yarn install warning. Sorry about the noise!

Changes

  • Remove workspaces from our package.json to silence a Yarn warning (@​timdorr)
reduxjs/redux

v4.2.0

Compare Source

This release marks the original createStore API as @deprecated to encourage users to migrate to Redux Toolkit, and adds a new legacy_createStore API as an alias without the deprecation warning.

Goal

Redux Toolkit (the @reduxjs/toolkit package) is the right way for Redux users to write Redux code today:

https://redux.js.org/introduction/why-rtk-is-redux-today

Unfortunately, many tutorials are still showing legacy "hand-written" Redux patterns, which result in a much worse experience for users. New learners going through a bootcamp or an outdated Udemy course just follow the examples they're being shown, don't know that RTK is the better and recommended approach, and don't even think to look at our docs.

Given that, the goal is to provide them with a visual indicator in their editor, like createStore . When users hover over the createStore import or function call, the doc tooltip recommends using configureStore from RTK instead, and points them to that docs page. We hope that new learners will see the strikethrough, read the tooltip, read the docs page, learn about RTK, and begin using it.

To be extremely clear:

WE ARE NOT GOING TO ACTUALLY REMOVE THE createStore API, AND ALL YOUR EXISTING CODE WILL STILL CONTINUE TO WORK AS-IS!

We are just marking createStore as "deprecated":

"the discouragement of use of some feature or practice, typically because it has been superseded or is no longer considered efficient or safe, without completely removing it or prohibiting its use"

For additional details, see the extensive discussion in https://github.com/reduxjs/redux/issues/4325 .

Rationale

  • RTK provides a vastly improved Redux usage experience, with APIs that simplify standard usage patterns and eliminate common bugs like accidental mutations
  • We've had suggestions to merge all of RTK into the redux core package, or fully deprecate the entire redux package and rename it to @reduxjs/core. Unfortunately, those bring up too many complexities:
    • We already had a package rename from redux-starter-kit to @reduxjs/toolkit, and all of our docs and tutorials have pointed to it for the last three years. I don't want to put users through another whiplash package transition for no real benefit
    • Merging or rearranging our packages would effectively require merging all of the Redux repos into a single monorepo. That would require hundreds of hours of effort from us maintainers, including needing to somehow merge all of our docs sites together. We don't have the time to do that.
  • I don't want to add runtime warnings that would be really annoying

So, this is the minimum possible approach we can take to reach out to users who otherwise would never know that they are following outdated patterns, while avoiding breaking running user code or having to completely rewrite our package and repo structure.

Results

When a user imports createStore in their editor, they will see a visual strikethrough. Hovering over it will show a doc tooltip that encourages them to use configureStore from RTK, and points to an explanatory docs page:

image

Again, no broken code, and no runtime warnings.

If users do not want to see that strikethrough, they have three options:

  • Follow our suggestion to switch over to Redux Toolkit and configureStore
  • Do nothing. It's just a visual strikethrough, and it doesn't affect how your code behaves. Ignore it.
  • Switch to using the legacy_createStore API that is now exported, which is the exact same function but with no @deprecation tag. The simplest option is to do an aliased import rename:

image

What's Changed

Full Changelog: reduxjs/redux@v4.1.2...v4.2.0

v4.1.2

Compare Source

This release fixes a small specific TS types issue where state types that had a nested unknown field inside would cause compilation failures when used as the preloadedState argument.

What's Changed

Full Changelog: reduxjs/redux@v4.1.1...v4.1.2

reduxjs/redux-thunk

v2.4.2

Compare Source

This release removes an unused TS type that caused errors when users were type-checking libraries in node_modules.

What's Changed

Full Changelog: reduxjs/redux-thunk@v2.4.1...v2.4.2

v2.4.1

Compare Source

This release adds an explicit plain action overload to the ThunkDispatch TS type to better handle inference of the return value in some cases.

What's Changed

Full Changelog: reduxjs/redux-thunk@v2.4.0...v2.4.1

v2.4.0

Compare Source

This very overdue release makes several major improvements to the TypeScript types, and converts the actual source to TypeScript. Sorry for the delay!

Changelog

TypeScript Improvements

This release fixes several outstanding issues that had been reported with the types. An extra overload has been added to let TS correctly understand some generically-typed values being passed to dispatch, and the overloads have been reworked for additional compatibility.

There's also a new ThunkActionDispatch type that can be used to represent how bindActionCreators turns bound thunks into (arg) => thunkReturnValue.

Additionally, all of the generic args have been giving meaningful names instead of one-letter abbreviations (S -> State, E -> ExtraArgument, etc), and we've added descriptive comments in the type definitions for clarity.

Optional Global Dispatch Type Extension

Most Redux apps have the thunk middleware enabled, but the default Dispatch and bindActionCreator types only know about the standard behavior of a basic Redux store without any middleware. The thunk middleware types add to that type behavior, so that Dispatch knows dispatching a thunk can actually return a value such as a Promise.

We generally recommend inferring the type of dispatch and using that to create reusable types, including creating pre-typed hooks. However, some users may prefer to globally augment the Dispatch type to always use the additional thunk behavior.

You can now import 'redux-thunk/extend-redux' to globally augment the Dispatch type as an opt-in change in behavior.

Codebase Converted to TypeScript

We've gone ahead and converted the actual source to TS. Since the source was only 15-ish lines to begin with, most of the "conversion" time was just trying to convince TS that assigning thunk.extraArgument = createThunkMiddleware was a legal operation :)

We also updated the build tooling:

  • Babel updates
  • Rollup for the UMDs instead of Webpack
  • Github Actions for CI instead of Travis

Finally, the README has been updated with newer instructions and usage information.

What's Changed

New Contributors

Full Changelog: reduxjs/redux-thunk@v2.3.0...v2.4.0

vercel/serve

v12.0.1

Compare Source

Changes
  • HTTPS: Adding Ability to Send Passphrase to createServer: #​655
  • Fix network not being shown anymore: #​661
Credits

Huge thanks to @​wilbert-abreu and @​marcofugaro for helping!

styled-components/styled-components

v5.3.6

Compare Source

What's Changed
Deprecations
  • $as and $forwardedAs will be removed in the next major version, use the unprefixed props instead
New Contributors

Full Changelog: styled-components/styled-components@v5.3.5...v5.3.6

v5.3.5

Add statement of solidarity against the war on Ukraine 🇺🇦

v5.3.3

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v5.3.1...v5.3.3

Microsoft/TypeScript

v4.9.3: TypeScript 4.9

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

Changes:

See More
  • 3d2b401 Fix assertion functions accessed via wildcard imports (#​51324)
  • 64d0d5a fix(51301): Fixing an unused import at the end of a line removes the newline (#​51320)
  • 754eeb2 Update CodeQL workflow and configuration, fix found bugs (#​51263)
  • d8aad26 Update package-lock.json
  • d4f26c8 fix(51245): Class with parameter decorator in arrow function causes "convert to default export" refactoring failure (#​51256)
  • 16faf45 Update package-lock.js

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the renovate label Feb 29, 2020
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from dc5ca12 to c82d2c6 Compare March 7, 2020 01:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 12 times, most recently from 6f9ea4a to 1f6e377 Compare March 19, 2020 18:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from eafa8fa to d22925d Compare March 26, 2020 19:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d22925d to 0d541e4 Compare March 26, 2020 23:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from e9da845 to 27b7505 Compare October 4, 2021 12:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 74e6130 to 0a76df2 Compare October 12, 2021 19:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from c1f9b4c to 146c205 Compare October 21, 2021 04:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from f475d67 to 50ab47c Compare October 28, 2021 22:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from de22b4d to 139bba2 Compare March 7, 2022 15:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 139bba2 to 69a2dc4 Compare March 26, 2022 15:24
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 69a2dc4 to 0ea0db2 Compare April 24, 2022 18:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0ea0db2 to f5e1055 Compare May 15, 2022 23:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f5e1055 to 67b0812 Compare June 18, 2022 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants