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-package-history #164

Closed
wants to merge 1 commit into from
Closed

update-package-history #164

wants to merge 1 commit into from

Conversation

liubiantao
Copy link
Member

Peer react-router@1.0.3 wants history@^1.17.0

Peer react-router@1.0.3 wants history@^1.17.0
@liubiantao
Copy link
Member Author

贴个changelog,以防以后出问题

https://github.com/rackt/history/blob/master/CHANGES.md

v1.17.0

Dec 19, 2015

  • Bugfix: Don't throw in memory history when out of history entries (#170)
  • Bugfix: Fix the deprecation warnings on createPath and createHref (#189)

v1.16.0

Dec 10, 2015

  • Bugfix: Silence all warnings that were introduced since 1.13 (see rackt/react-router#2682)
  • Deprecation: Deprecate the createLocation method in the top-level exports
  • Deprecation: Deprecate the state arg to history.createLocation

v1.15.0

Dec 7, 2015

  • Feature: Accept location descriptors in createPath and createHref (#173)
  • Deprecation: Deprecate the query arg to createPath and createHref in favor of using location descriptor objects (#173)

v1.14.0

Dec 6, 2015

  • Feature: Accept objects in history.push and history.replace (#141)
  • Deprecation: Deprecate history.pushState and history.replaceState in favor of passing objects to history.push and history.replace (#168)
  • Bugfix: Disable browser history on Chrome iOS (#146)
  • Bugfix: Do not convert same-path PUSH to REPLACE if the hash has changed (#167)
  • Add ES2015 module build (#152)
  • Use query-string module instead of qs to save on bytes (#121)

v1.13.1

Nov 13, 2015

  • Fail gracefully when Safari security settings prevent access to window.sessionStorage
  • Pushing the currently active path will result in a replace to not create additional browser history entries (#43)
  • Strip the protocol and domain from <base href> (#139)

@idisblueflash
Copy link
Contributor

等后台服务器好了,再测试看看。现在测不出来router的问题。
原因:我点击了heroku的测试链接,那个链接访问国内api不行。

@idisblueflash
Copy link
Contributor

@liubiantao 我很好奇,为什么要把react-router升级到1.0.3?

@idisblueflash
Copy link
Contributor

打开: https://yaopai-mobile-pr-pr-164.herokuapp.com
无法读取数据,无法测试。
但是本地可以。测试页面跳转和各级跳转时,没有问题。

@idisblueflash
Copy link
Contributor

package.json文件里并没有升级react-router.
所以,我觉得这个PR没有必要。

@idisblueflash idisblueflash deleted the update-package-history branch January 8, 2016 15:02
@liubiantao liubiantao restored the update-package-history branch January 9, 2016 08:00
@liubiantao
Copy link
Member Author

这个我不是在微信里给你说了吗

@idisblueflash idisblueflash requested a deployment to yaopai-mobile-pr-pr-167 January 9, 2016 08:02 Pending
@liubiantao liubiantao deleted the update-package-history branch January 9, 2016 08:02
@idisblueflash
Copy link
Contributor

我上岁数啦,知道有这回事,但是具体忘记了。所以在这里再明确一下。

@liubiantao
Copy link
Member Author

这个修复的是npm install的问题,ci已经挂了好几天了,你从Files change里面可以看到我没有把react-router升级到1.0.3,这是系统自动升级的,版本号最后一位代表bugfix,根据我们的package.json文件,我们只能保证版本号前两位一样,最后一位永远都会保持最新,而目前最新的就是1.0.3。

@liubiantao
Copy link
Member Author

"bluebird": "~3.1.1" 表示会安装最新的补丁版本。比如:安装 3.1.2、3.1.3 等,但是不会安装 3.2.0 这种小版本或者4.0.0 这种大版本(就算这些版本是最新的)。这种表示法是比较保险的,因为补丁版本只是 bug 修复,不会新增功能。
"request-promise": "^1.0.2" 表示会安装最新的补丁版本或者小版本。比如:安装 1.1.0、1.1.1 等小版本,或者 1.0.3、1.0.4 等补丁版本,但是不会安装 2.0.0 这种大版本。而且,总是安装版本号最大的(也就是优先安装小版本)。这种表示法通常是保险的,小版本会增加向后兼容的功能。

https://mp.weixin.qq.com/s?__biz=MjM5NTEwMTAwNg==&mid=401620478&idx=1&sn=87b110531c1a5b5a093bd909d874cdcd&scene=1&srcid=0109xLojYCC9isKPLgsFU6oh&key=41ecb04b05111003f7ca2d7de61d71e01c484628eaf2a3cbeba349644003e3e211ed68608e2550cc46d9261660006c87&ascene=0&uin=MjA1MTAxODU%3D&devicetype=iMac+MacBookPro11%2C1+OSX+OSX+10.10.5+build(14F1509)&version=11020201&pass_ticket=4wTWWBg810S8LmhFy8HbrNxwURweiUqkM7j%2F%2F8z2o0s%3D

@idisblueflash
Copy link
Contributor

我记得package.json文件里,版本号三位都可以定死。需求新版本,有可能引入了新的组件?

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.

2 participants