Skip to content
This repository was archived by the owner on Jun 26, 2020. It is now read-only.
This repository was archived by the owner on Jun 26, 2020. It is now read-only.

Consolidate packages #489

Closed
Closed

Description

@gaearon

Currently there's a lot of forking going on which makes it harder to figure out how everything fits together. For example:

  • Injecting into the hook

    • React tries to do this here
    • But actually the hook doesn't exist yet until injected so RN just copies the same code here
  • Setting up the connection

  • Nuclide vendors the Electron build for the Inspector (although it only uses the client while RN runs its fork of the server).

  • Backends depend on React internals but aren’t colocated with React


The goals for consolidation:

  • Reduce the number of forks to make it easier to make changes across them (e.g. to support Fiber).
  • Make it easy for downstream packages (RN, Nuclide) to accept changes related to DevTools by packaging them.
  • Consolidate the code relying on React internal data structure inside the React repo.

The plan for consolidation:

Activity

  1. gaearon commented on Feb 7, 2017

    @gaearon
    ContributorAuthor

    cc @jhen0409, do you have any feedback on this plan? Would it help you to simplify anything in react-native-debugger?

  2. gaearon commented on Feb 7, 2017

    @gaearon
    ContributorAuthor

    Some initial work in #494.

  3. jhen0409 commented on Feb 8, 2017

    @jhen0409
    Contributor

    This is a good news!

    Just wondering we could provide Panel component in react-devtools-core? Currently I used it for react-native-debugger with forked server setup, I want to avoid some console.log and all DOM manipulation for use react inspector. If you agree:

    • To avoid Panel use another react instance, add react to externals for standalone config, and export Panel
    • Or a new component webpack config
  4. gaearon commented on Feb 8, 2017

    @gaearon
    ContributorAuthor

    Is there anything in particular we could fix in standalone that would make it good for you? For example we could easily remove logs. Is there something else annoying you?

  5. jhen0409 commented on Feb 8, 2017

    @jhen0409
    Contributor

    @gaearon, looks like it just a little problem, I don't want to set #loading-status (It also not explained in the readme), I simply made a PR for that. #497

  6. gaearon commented on Feb 8, 2017

    @gaearon
    ContributorAuthor

    @jhen0409 Published 2.0 with setStatusListener(), do you need anything else? Happy to do more changes.

  7. bvaughn commented on Aug 19, 2019

    @bvaughn
    Contributor

    React DevTools has been rewritten and recently launched a new version 4 UI. The source code for this rewrite was done in a separate repository and now lives in the main React repo (github.com/facebook/react).

    Because version 4 was a total rewrite, and all issues in this repository are related to the old version 3 of the extension, I am closing all issues in this repository. If you can still reproduce this issue, or believe this feature request is still relevant, please open a new issue in the React repo: https://github.com/facebook/react/issues/new?labels=Component:%20Developer%20Tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions