Hey there!
There are downstream projects (the one I have my eye on is @nteract/outputs that could use a version of react-json-tree that doesn't have a dependency on babel-runtime.
Would it be possible to release a new version of react-json-tree?
EDIT 20200721: updated nteract/outputs link
Can we please do this? We've had to clone the repo because you can't run babel 7 with this project because it specifies babel 6 as a dependency. We just need somebody to publish the code thats in the repo
@timdorr What is the plan for publishing? It seems like we should publish:
react-json-tree: 0.12.0 (resolves https://github.com/reduxjs/redux-devtools/issues/480, https://github.com/reduxjs/redux-devtools/issues/490 (and https://github.com/reduxjs/redux-devtools/issues/487 if we get https://github.com/reduxjs/redux-devtools/pull/513 merged))redux-devtools-inspector: 0.12.0 (with react-json-tree at 0.12.0) (resolves https://github.com/reduxjs/redux-devtools/issues/481, https://github.com/reduxjs/redux-devtools/issues/497)redux-devtools: 3.6.0 (resolves https://github.com/reduxjs/redux-devtools/issues/473)No specific plan. I haven't yet looked through the state of the code right now to know if they should be published and at what version (patch vs minor vs major).
Maybe we can do a quick RC release so they don't show up on the latest npm tag and and break things for folks without some testing first. Plus, that will make sure I know how to publish these libraries (in case there are different steps than I'm used to)
Makes sense. I've compiled an exhaustive changelog and made sure to find any changes since the last published version of the package (even packages that were last published from their original repo). Hopefully that will help with the publish. I've included a short summary under each change where appropriate.
Overall, it looks like almost all of the changes were internal changes (https://github.com/reduxjs/redux-devtools/pull/449 looks like mostly linting and converting tests to Jest). Before the PRs you merged, I don't think there had been any unpublished bug fixes or feature changes. redux-devtools-inspector is the only package that has changes in the published package that haven't been made in this repo, and the only package that would cause a regression if published right now.
babel-runtime as dependencyprepare npm script for internal useremotedev to redux-devtools for two constantscolor dependency from ^1.0.1 to ^2.0.0prop-types dependency from ^15.5.10 to ^15.6.0react-icons dependency from ^2.2.5 to ^2.2.7react-jsonschema-form dependency from ^0.48.2 to ^1.0.0react-select dependency from ^1.0.0-rc.5 to ^1.0.0-rc.10styled-components dependency from ^2.0.0 to ^2.2.2remotedev-inspector-monitor to redux-devtools-inspectorreact dependency from ^15.1.0 to ^16.4.0@timdorr After thinking about it a little more, I think it would make sense to just publish react-json-tree (in order to resolve https://github.com/reduxjs/redux-devtools/issues/480 and https://github.com/reduxjs/redux-devtools/issues/490 (and maybe https://github.com/reduxjs/redux-devtools/issues/487)) and redux-devtools (in order to resolve https://github.com/reduxjs/redux-devtools/pull/482).
redux-devtools-inspector can't be published until https://github.com/reduxjs/redux-devtools/issues/430 and https://github.com/reduxjs/redux-devtools/issues/431 are resolved in order to avoid a regression.
Based on https://github.com/reduxjs/redux-devtools/issues/454#issuecomment-456973394, I don't think redux-devtools-core or redux-devtools-cli are finished yet, and so there's no need to publish those.
The rest of the packages don't have any non-internal changes.
I don't know if it's helpful or not but here's a graph of the different repos getting merged together and the commit history since then: https://methuselah96.github.io/redux-devtools-app-testing/ (ignore the commit hashes and author). The last published version of each package is tagged.
Any updates here? I'd love an update - we're getting warnings in our test runs about deprecated React methods.
No updates from me. @timdorr Is there anything I can do to help publish? I have a bit of free time on my hands and if I knew that fixes/changes will get published at some point it would help motivate me to work on this project more.
Hey @zalmoxisus or @alexkuz, can either of you grant me contributor access on npm? I'd like to help @Methuselah96 to get these updates published.
@zalmoxisus @alexkuz @gaearon @jhen0409 @romseguy More specifically, the packages it would be great to have npm access to are:
Already in this monorepo/organization:
react-json-tree (@alexkuz, @gaearon, @zalmoxisus)redux-devtools-core (@zalmoxisus)redux-slider-monitor (@jhen0409) (rename to redux-devtools-slider-monitor?)redux-devtools-inspector (@alexkuz, @zalmoxisus)devui (@zalmoxisus)redux-devtools-cli (@zalmoxisus)d3tooltip (@romseguy)map2tree (@romseguy)d3-state-visualizer (@romseguy)redux-devtools-chart-monitor (@romseguy)redux-devtools-test-generator (@zalmoxisus)redux-devtools-trace-monitor (@zalmoxisus)Hope to move to this monorepo:
redux-devtools-extension (@zalmoxisus)react-base16-styling (@alexkuz)base16 (@gaearon)redux-devtools-themes (@gaearon)remotedev-serialize (@zalmoxisus) (we might rename this one anyway)We already have npm access to (no action required):
redux-devtools-instrumentredux-devtoolsredux-devtools-log-monitorYou can give access to timdorr and/or methuselah96 on npm.
Hey guys! Thanks for all the effort here!
I granted access to @timdorr and @Methuselah96:
redux-slider-monitord3-state-visualizermap2treereact-json-treed3tooltipredux-devtools-chart-monitorredux-devtools-inspectorredux-devtools-test-generatorredux-devtools-extensionremotedev-serializedevuiredux-devtools-trace-monitorredux-devtools-coreredux-devtools-cliAlso for redux-devtools-dock-monitor, which is not used for the extension (and it's not in the list), but many are using it for "vanilla Redux Devtools".
Let me know if I missed some that I have access.
@zalmoxisus Thanks for your help, that looks great!
@alexkuz The only one left that it would be nice to have access to from you is react-base16-styling. Can you get us npm access for that as well?
@timdorr @Methuselah96 here you are :) Thank you!
Most helpful comment
Published: https://github.com/reduxjs/redux-devtools/releases/tag/react-json-tree%400.12.0