{"action":"closed","issue":{"url":"https://api.github.com/repos/babel/notes/issues/44","repository_url":"https://api.github.com/repos/babel/notes","labels_url":"https://api.github.com/repos/babel/notes/issues/44/labels{/name}","comments_url":"https://api.github.com/repos/babel/notes/issues/44/comments","events_url":"https://api.github.com/repos/babel/notes/issues/44/events","html_url":"https://github.com/babel/notes/issues/44","id":272008353,"number":44,"title":"Meta: create a tool to upgrade users to Babel 7","user":{"login":"hzoo","id":588473,"avatar_url":"https://avatars1.githubusercontent.com/u/588473?v=4","gravatar_id":"","url":"https://api.github.com/users/hzoo","html_url":"https://github.com/hzoo","followers_url":"https://api.github.com/users/hzoo/followers","following_url":"https://api.github.com/users/hzoo/following{/other_user}","gists_url":"https://api.github.com/users/hzoo/gists{/gist_id}","starred_url":"https://api.github.com/users/hzoo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hzoo/subscriptions","organizations_url":"https://api.github.com/users/hzoo/orgs","repos_url":"https://api.github.com/users/hzoo/repos","events_url":"https://api.github.com/users/hzoo/events{/privacy}","received_events_url":"https://api.github.com/users/hzoo/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2017-11-07T22:30:36Z","updated_at":"2018-02-19T15:05:12Z","closed_at":"2018-02-19T15:05:11Z","author_association":"OWNER","body":"It would be something that would work for 90% of most users (not using babel-core directly or any crazy options), would love for the community to come together to help out with this, especially as everyone is trying to update to v7 (at least can comment on the kinds of issues you have faced to see if they can be automated).\r\n\r\nBecause most of this is json, we need a tool that handles json files.\r\n\r\nList of packages: https://gist.github.com/hzoo/3b78b8225ffddc34483785018664390e (not all have an equivalent because they can be new for v7)\r\n\r\n## Scoped packages\r\n- Rename packages in package.json\r\n  - Things like `\"babel-core\": \"6.26.0\" -> \"@babel/core\": \"7.0.0-beta.31\"` (support changing to the beta version or whatever is in the latest dist tag on npm)\r\n- Fix config in `.babelrc`\r\n  - `{ \"presets\": [\"env\"] }` -> `{ \"presets\": [\"@babel/env\"] }`\r\n\r\n## Renames\r\n\r\n- [#6575](https://github.com/babel/babel/pull/6575) Removed all `-es20xx-` prefixes from packages\r\n\r\n`babel-plugin-transform-es2015-classes` -> `babel-plugin-transform-classes`\r\n`transform-es3-member-expression-literals` -> `transform-member-expression-literals`\r\n\r\n- [#6573](https://github.com/babel/babel/pull/6573) Merged `transform-async-to-module-method` into `transform-async-to-generator` as an option\r\n\r\nchange package json, modify babelrc.\r\n\r\n- [#6570](https://github.com/babel/babel/pull/6570) Proposals are renamed\r\n\r\n`babel-plugin-transform-class-properties` -> `babel-plugin-proposal-class-properties`\r\n\r\n## Peer Dep on `@babel/core`\r\n\r\nThis means if there wasn't a `@babel/core` at the top level, it should be added in package.json\r\n\r\n## .babelrc.js\r\n\r\nNot sure if we have to do this, not reason to change if it's not necessary.\r\n\r\nI think if they are using the \"env\" key a lot we could change it. The reason why we can change the config in the first place is because it's json and not js\r\n\r\n## `@babel/node`\r\n\r\n> I think we should probably add `@babel/node` back as a dependency in cli anyway\r\n\r\nAdd `@babel/node` as a dependency if they are using it in scripts."}}
{"actor":{"display_login":"hzoo"}}