{"action":"created","issue":{"url":"https://api.github.com/repos/ReactTraining/react-router/issues/4048","repository_url":"https://api.github.com/repos/ReactTraining/react-router","labels_url":"https://api.github.com/repos/ReactTraining/react-router/issues/4048/labels{/name}","comments_url":"https://api.github.com/repos/ReactTraining/react-router/issues/4048/comments","events_url":"https://api.github.com/repos/ReactTraining/react-router/issues/4048/events","html_url":"https://github.com/ReactTraining/react-router/issues/4048","id":183169306,"number":4048,"title":"yarn doesn't resolve to the beta releases ","user":{"login":"volkanunsal","id":151600,"avatar_url":"https://avatars.githubusercontent.com/u/151600?v=3","gravatar_id":"","url":"https://api.github.com/users/volkanunsal","html_url":"https://github.com/volkanunsal","followers_url":"https://api.github.com/users/volkanunsal/followers","following_url":"https://api.github.com/users/volkanunsal/following{/other_user}","gists_url":"https://api.github.com/users/volkanunsal/gists{/gist_id}","starred_url":"https://api.github.com/users/volkanunsal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/volkanunsal/subscriptions","organizations_url":"https://api.github.com/users/volkanunsal/orgs","repos_url":"https://api.github.com/users/volkanunsal/repos","events_url":"https://api.github.com/users/volkanunsal/events{/privacy}","received_events_url":"https://api.github.com/users/volkanunsal/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-10-14T23:10:22Z","updated_at":"2016-10-21T14:49:12Z","closed_at":"2016-10-15T03:33:19Z","body":"I'm using the `beta` release, version 3.0.0-beta.1. When I install this via npm, everything works as expected, but when I run `yarn`, it loads the uncompiled version of the library. I'm not sure what your release process entails, but I thought I'd report it here since it seems to be only happening with this repo, and for this particular release tag. \r\n\r\nThis is the relevant bit in the `yarn.lock` file.\r\n\r\n```\r\nreact-router@beta:\r\n  version \"3.0.0-beta.1\"\r\n  resolved \"https://registry.yarnpkg.com/react-router/-/react-router-3.0.0-beta.1.tgz#eb3019587da65ac77c12cf6ab790d408247ad5af\"\r\n  dependencies:\r\n    history \"^3.0.0\"\r\n    hoist-non-react-statics \"^1.2.0\"\r\n    invariant \"^2.2.1\"\r\n    loose-envify \"^1.2.0\"\r\n    warning \"^3.0.0\"\r\n\r\n```"},"comment":{"url":"https://api.github.com/repos/ReactTraining/react-router/issues/comments/255397693","html_url":"https://github.com/ReactTraining/react-router/issues/4048#issuecomment-255397693","issue_url":"https://api.github.com/repos/ReactTraining/react-router/issues/4048","id":255397693,"user":{"login":"volkanunsal","id":151600,"avatar_url":"https://avatars.githubusercontent.com/u/151600?v=3","gravatar_id":"","url":"https://api.github.com/users/volkanunsal","html_url":"https://github.com/volkanunsal","followers_url":"https://api.github.com/users/volkanunsal/followers","following_url":"https://api.github.com/users/volkanunsal/following{/other_user}","gists_url":"https://api.github.com/users/volkanunsal/gists{/gist_id}","starred_url":"https://api.github.com/users/volkanunsal/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/volkanunsal/subscriptions","organizations_url":"https://api.github.com/users/volkanunsal/orgs","repos_url":"https://api.github.com/users/volkanunsal/repos","events_url":"https://api.github.com/users/volkanunsal/events{/privacy}","received_events_url":"https://api.github.com/users/volkanunsal/received_events","type":"User","site_admin":false},"created_at":"2016-10-21T14:49:12Z","updated_at":"2016-10-21T14:49:12Z","body":"This issue is still happening. It has nothing to do with Webpack, but probably with the way Yarn installs packages. It's a bit of a mystery to me right now, but I found this snippet about Yarn's architecture that explains it a little bit.\r\n\r\nThe [install process](https://code.facebook.com/posts/1840075619545360) is broken down into three steps:\r\n\r\n> \r\n> Resolution: Yarn starts resolving dependencies by making requests to the registry and recursively looking up each dependency.\r\n>\r\n> Fetching: Next, Yarn looks in a global cache directory to see if the package needed has already been downloaded. If it hasn't, **Yarn fetches the tarball for the package and places it in the global cache so it can work offline and won't need to download dependencies more than once.** Dependencies can also be placed in source control as tarballs for full offline installs.\r\n>\r\n> Linking: Finally, Yarn links everything together by copying all the files needed from the global cache into the local node_modules directory.\r\n\r\nSo, my guess is that the tarball of the beta release is not compiled, and so when we run `yarn add react-router@beta`, it takes the beta branch –– which must be uncompiled –– and caches it locally as a tarball.\r\n\r\nI'm currently solving this by re-installing `react-router` after every call to `yarn add`, but I figured it's something you might like to do something about. "}}
{"actor":{"display_login":"volkanunsal"}}