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

πŸš€ Update dependencies: Thu Apr 19 14:45:58 UTC 2018 #1

Closed
wants to merge 3 commits into from

Conversation

jaramir
Copy link
Owner

@jaramir jaramir commented Apr 19, 2018

πŸ€– Updated depedencies:

react ^15.0.0 β†’ 16.3.2

.16.3.2 / 2018-04-16

  • Add 16.3.2 changelog (#12621)
  • Update bundle sizes for 16.3.2 release
  • Update error codes for 16.3.2 release
  • Updating package versions for release 16.3.2
  • Updating yarn.lock file for 16.3.2 release
  • Fix documentation of the release process (#12337)
    • Adusted grammar in release script readme.
    • Adjusts title and explanation about the release process.
  • Fix small typos in create-subscription readme (#12399)
  • tests: add regression test for reading ReactCurrentOwner stateNode (#12412)
    • tests: add regression test for reading ReactCurrentOwner stateNode
    • tests: replace expect with just rendering the component
  • Update GCC (#12618)
  • Fixed debug performance labels for new component types (#12609)
    • Added new debug performance tests for AsyncMode, StrictMode, forwardRef, and context provider/consumer components.
    • Updated performance labels to exclude AsyncMode and StrictMode.
    • Added labels for forwardRef (and inner function) that mirror DevTools labels.
  • [Danger] Minor fixes (#12606)
    • Don't download bundle stats from master on CI
      This was temporarily necessary in the past because we didn't have the logic that downloads actual merge base stats.
      We do have that now as part of the Danger script. So we can remove this.
    • Use absolute threshold for whether to show a change
    • Download master stats, but only for other master builds
    • Rewrite sizes
  • Bump expiration for interactive updates to 150ms in production (#12599)
    • Bump expiration for interactive updates to 150ms in production
      what is the change?:
      Changes the expiration deadline from 500ms to 150ms, only in production.
      In development it will still be 500ms.
      I'm thinking we may want to change the 'bucket size' too, will look into
      that a bit.
      why make this change?:
      We need to ensure interactions are responsive enough in order to gather
      more test data on async. mode.
      test plan:
      No tests failed - where shall we add a test for this?
    • Add comments
  • Remove @providesModule in www shims
  • Added UMD build to test renderer package (#12594)
  • Fixes language in error message. (#12590)
  • createReactNativeComponentClass needs to be CommonJS
    oops
  • Refactor findHostInstance and findNodeHandle (#12575)
    • Move findNodeHandle into the renderers and use instantiation
      This is just like ReactDOM does it. This also lets us get rid of injection
      for findNodeHandle. Instead I move NativeMethodsMixin and ReactNativeComponent
      to use instantiation.
    • Refactor findHostInstance
      The reconciler shouldn't expose the Fiber data structure. We should pass
      the component instance to the reconciler, since the reconciler is the
      thing that is supposed to be instancemap aware.
    • Fix devtools injection
  • [RN] Move view config registry to shims (#12569)
    • Move view config registry to shims
      This ensures that both Fabric and RN renderers share the same view config
      registry since it is stateful.
      I had to duplicate in the mocks for testing.
    • Move createReactNativeComponentClass to shims and delete internal usage
      Since createReactNativeComponentClass is just an alias for the register
      there's no need to bundle it. This file should probably just move back
      to RN too.
  • Consolidate eventTypes registry with view configs (#12556)
    We already have one stateful module that contains all the view config.
    We might as well store the event types there too. That way the shared
    state is compartmentalized (and I can move it out in a follow up PR).
    The view config registry also already has an appropriate place to call
    processEventTypes so now we no longer have to do it in RN.
    Will follow up with a PR to RN to remove that call.
  • [RN] Remove unstable_batchedUpdates and unmountComponentAtNodeAndRemoveContainer from Fabric (#12571)
    These don't make much sense in Fabric, since Fabric will be async by default only.
    And unmount+remove container is a sketchy API we should remove so we might
    as well make sure modern containers enforce that.
  • Remove ReactNativePropRegistry (#12559)
    This has always been an unnecessary indirection to protect opaqueness,
    which hasn't really worked out.
  • Allocate unique reactTags for RN and Fabric (#12587)
    Took this opportunity to remove some abstract overhead.
    In Fabric it is extra simple since they no longer overlap with root tags.
  • Throw more specific error if passed undefined in React.cloneElement (#12534)
    • throw error if passed undefined
    • should be TypeError
    • simplify
    • use invariant
    • editor messed up spacing
    • better check
    • Revert "better check"
      This reverts commit 273370758eafa54d329577b3dc942c70587eccd3.
    • yarn prettier test was failing
    • more explicit copy
    • es6 import
    • tests
    • formatting
    • Move import
  • Unfork invariant and instead use it from reactProdInvariant (#12585)
  • Preserve error codes for invariants on www (#12539)
    • Preserve error codes for invariants on www
    • Remove unintentional change
  • Must be a before PlacementAndUpdate (#12580)
  • Keep consistency in the comment (#12579)
  • [RN] Move takeSnapshot to RN (#12574)
    It only uses public APIs. I have a diff on the other side.
  • Support findNodeHandle in Fabric (#12573)
    This doesn't actually need to share any state because it goes through
    the instance to the fiber structure. Since Fabric is on the same version
    as RN, calling it on either renderer works.
  • Remove flushSync from React Native (#12565)
    There are no plans to enable async in the old renderer. In the new renderer
    it only really makes sense to do from the main thread and probably from
    native since it'll have to yield to native first.
  • Bug fix
  • Move TouchHistoryMath to React Native repo (#12557)
    This isn't used by React core and is just a pure helper so it might as
    well live where it's used. The React Native repo.
  • Expose component stack from reactTag to React Native renderer (#12549)
    This is not safe in general and therefore shouldn't be exposed to anything
    other than React Native internals.
    It will also need a different version in Fabric that will not have the
    reactTag exposed.
  • Clarify ReactDOM's case warning for html tags (#12533)
    • update warning text
    • update tests to match
    • yarn prettier
    • include note on HTML5 custom elements
    • dan’s copy suggestion
    • remove β€˜letters’
  • Removed Array.from() usage (#12546)
  • Removed duplicate typeof check (#12541)
  • facebook.github.io/react -> reactjs.org (#12545)
  • Don't render bitmask-bailing consumers even if there's a deeper matching child (#12543)
    • Don't render consumers that bailed out with bitmask even if there's a deeper matching child
    • Use a render prop in the test
      Without it, doesn't do anything because we bail out on constant element anyway.
      That's not what we're testing, and could be confusing.
  • Add a build step to hoist warning conditions (#12537).

@jaramir jaramir changed the title πŸš€ Update dependencies: Thu Apr 19 13:49:30 UTC 2018 πŸš€ Update dependencies: Thu Apr 19 13:50:16 UTC 2018 Apr 19, 2018
@jaramir
Copy link
Owner Author

jaramir commented Apr 19, 2018

πŸ€– Updated depedencies:

react 15.1.1 β†’ 16.3.2

.16.3.2 / 2018-04-16

  • Add 16.3.2 changelog (#12621)
  • Update bundle sizes for 16.3.2 release
  • Update error codes for 16.3.2 release
  • Updating package versions for release 16.3.2
  • Updating yarn.lock file for 16.3.2 release
  • Fix documentation of the release process (#12337)
    • Adusted grammar in release script readme.
    • Adjusts title and explanation about the release process.
  • Fix small typos in create-subscription readme (#12399)
  • tests: add regression test for reading ReactCurrentOwner stateNode (#12412)
    • tests: add regression test for reading ReactCurrentOwner stateNode
    • tests: replace expect with just rendering the component
  • Update GCC (#12618)
  • Fixed debug performance labels for new component types (#12609)
    • Added new debug performance tests for AsyncMode, StrictMode, forwardRef, and context provider/consumer components.
    • Updated performance labels to exclude AsyncMode and StrictMode.
    • Added labels for forwardRef (and inner function) that mirror DevTools labels.
  • [Danger] Minor fixes (#12606)
    • Don't download bundle stats from master on CI
      This was temporarily necessary in the past because we didn't have the logic that downloads actual merge base stats.
      We do have that now as part of the Danger script. So we can remove this.
    • Use absolute threshold for whether to show a change
    • Download master stats, but only for other master builds
    • Rewrite sizes
  • Bump expiration for interactive updates to 150ms in production (#12599)
    • Bump expiration for interactive updates to 150ms in production
      what is the change?:
      Changes the expiration deadline from 500ms to 150ms, only in production.
      In development it will still be 500ms.
      I'm thinking we may want to change the 'bucket size' too, will look into
      that a bit.
      why make this change?:
      We need to ensure interactions are responsive enough in order to gather
      more test data on async. mode.
      test plan:
      No tests failed - where shall we add a test for this?
    • Add comments
  • Remove @providesModule in www shims
  • Added UMD build to test renderer package (#12594)
  • Fixes language in error message. (#12590)
  • createReactNativeComponentClass needs to be CommonJS
    oops
  • Refactor findHostInstance and findNodeHandle (#12575)
    • Move findNodeHandle into the renderers and use instantiation
      This is just like ReactDOM does it. This also lets us get rid of injection
      for findNodeHandle. Instead I move NativeMethodsMixin and ReactNativeComponent
      to use instantiation.
    • Refactor findHostInstance
      The reconciler shouldn't expose the Fiber data structure. We should pass
      the component instance to the reconciler, since the reconciler is the
      thing that is supposed to be instancemap aware.
    • Fix devtools injection
  • [RN] Move view config registry to shims (#12569)
    • Move view config registry to shims
      This ensures that both Fabric and RN renderers share the same view config
      registry since it is stateful.
      I had to duplicate in the mocks for testing.
    • Move createReactNativeComponentClass to shims and delete internal usage
      Since createReactNativeComponentClass is just an alias for the register
      there's no need to bundle it. This file should probably just move back
      to RN too.
  • Consolidate eventTypes registry with view configs (#12556)
    We already have one stateful module that contains all the view config.
    We might as well store the event types there too. That way the shared
    state is compartmentalized (and I can move it out in a follow up PR).
    The view config registry also already has an appropriate place to call
    processEventTypes so now we no longer have to do it in RN.
    Will follow up with a PR to RN to remove that call.
  • [RN] Remove unstable_batchedUpdates and unmountComponentAtNodeAndRemoveContainer from Fabric (#12571)
    These don't make much sense in Fabric, since Fabric will be async by default only.
    And unmount+remove container is a sketchy API we should remove so we might
    as well make sure modern containers enforce that.
  • Remove ReactNativePropRegistry (#12559)
    This has always been an unnecessary indirection to protect opaqueness,
    which hasn't really worked out.
  • Allocate unique reactTags for RN and Fabric (#12587)
    Took this opportunity to remove some abstract overhead.
    In Fabric it is extra simple since they no longer overlap with root tags.
  • Throw more specific error if passed undefined in React.cloneElement (#12534)
    • throw error if passed undefined
    • should be TypeError
    • simplify
    • use invariant
    • editor messed up spacing
    • better check
    • Revert "better check"
      This reverts commit 273370758eafa54d329577b3dc942c70587eccd3.
    • yarn prettier test was failing
    • more explicit copy
    • es6 import
    • tests
    • formatting
    • Move import
  • Unfork invariant and instead use it from reactProdInvariant (#12585)
  • Preserve error codes for invariants on www (#12539)
    • Preserve error codes for invariants on www
    • Remove unintentional change
  • Must be a before PlacementAndUpdate (#12580)
  • Keep consistency in the comment (#12579)
  • [RN] Move takeSnapshot to RN (#12574)
    It only uses public APIs. I have a diff on the other side.
  • Support findNodeHandle in Fabric (#12573)
    This doesn't actually need to share any state because it goes through
    the instance to the fiber structure. Since Fabric is on the same version
    as RN, calling it on either renderer works.
  • Remove flushSync from React Native (#12565)
    There are no plans to enable async in the old renderer. In the new renderer
    it only really makes sense to do from the main thread and probably from
    native since it'll have to yield to native first.
  • Bug fix
  • Move TouchHistoryMath to React Native repo (#12557)
    This isn't used by React core and is just a pure helper so it might as
    well live where it's used. The React Native repo.
  • Expose component stack from reactTag to React Native renderer (#12549)
    This is not safe in general and therefore shouldn't be exposed to anything
    other than React Native internals.
    It will also need a different version in Fabric that will not have the
    reactTag exposed.
  • Clarify ReactDOM's case warning for html tags (#12533)
    • update warning text
    • update tests to match
    • yarn prettier
    • include note on HTML5 custom elements
    • dan’s copy suggestion
    • remove β€˜letters’
  • Removed Array.from() usage (#12546)
  • Removed duplicate typeof check (#12541)
  • facebook.github.io/react -> reactjs.org (#12545)
  • Don't render bitmask-bailing consumers even if there's a deeper matching child (#12543)
    • Don't render consumers that bailed out with bitmask even if there's a deeper matching child
    • Use a render prop in the test
      Without it, doesn't do anything because we bail out on constant element anyway.
      That's not what we're testing, and could be confusing.
  • Add a build step to hoist warning conditions (#12537).

@jaramir jaramir changed the title πŸš€ Update dependencies: Thu Apr 19 13:50:16 UTC 2018 πŸš€ Update dependencies: Thu Apr 19 13:51:09 UTC 2018 Apr 19, 2018
@jaramir jaramir changed the title πŸš€ Update dependencies: Thu Apr 19 13:51:09 UTC 2018 πŸš€ Update dependencies: Thu Apr 19 14:45:58 UTC 2018 Apr 19, 2018
@jaramir jaramir closed this Apr 19, 2018
@jaramir jaramir deleted the update_dependencies_bot branch April 19, 2018 14:48
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.

1 participant