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 patching components #1067

Merged
merged 2 commits into from
Feb 12, 2017
Merged

Fix patching components #1067

merged 2 commits into from
Feb 12, 2017

Conversation

dbo
Copy link
Contributor

@dbo dbo commented Feb 10, 2017

The current code still fails on non-writable render on the prototype. This PR should fix this.

@arunoda Please have a look.

* zeit/master: (109 commits)
  ensure not to render ErrorDebug on production (#1064)
  switch octal format (#1060)
  Write executable files to `dist/bin` (#1059)
  [WIP] Migrate from Gulp to Fly (#965)
  wrong position of babel config example (#1057)
  Using router example improvements (#1034)
  Set displayName properly when patching React locally. (#1053)
  add react and react-dom to devDependencies again
  Using styled-jsx for with-jest example. (#1052)
  Testing: use a better way to get a port to the test app (#753)
  Update table of contents (#1051)
  Add table of contents to README (#735)
  TypeScript example proposal (#845)
  Throw when parsedUrl is not provided (#1015)
  Add support to transpile import/export syntax (#1044)
  add next/error (#1040)
  fix .baberc (#1041)
  add react and react-dom to devDependencies
  Add babel-preset-latest support. (#1027)
  add react and react dom as peer (#1024)
  ...
@dbo
Copy link
Contributor Author

dbo commented Feb 11, 2017

@arunoda Will this issue be fixed for 2.0? The current betas are still not usable for us (in dev mode); we're still on beta-13.

@arunoda
Copy link
Contributor

arunoda commented Feb 12, 2017

Yep. We can take this in.

@arunoda arunoda merged commit e38d81e into vercel:master Feb 12, 2017
@arunoda
Copy link
Contributor

arunoda commented Feb 12, 2017

Thanks.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants