{"action":"created","issue":{"url":"https://api.github.com/repos/rollup/rollup/issues/337","labels_url":"https://api.github.com/repos/rollup/rollup/issues/337/labels{/name}","comments_url":"https://api.github.com/repos/rollup/rollup/issues/337/comments","events_url":"https://api.github.com/repos/rollup/rollup/issues/337/events","html_url":"https://github.com/rollup/rollup/issues/337","id":119841302,"number":337,"title":"Isn’t jsnext:main too broad?","user":{"login":"rauschma","id":526114,"avatar_url":"https://avatars.githubusercontent.com/u/526114?v=3","gravatar_id":"","url":"https://api.github.com/users/rauschma","html_url":"https://github.com/rauschma","followers_url":"https://api.github.com/users/rauschma/followers","following_url":"https://api.github.com/users/rauschma/following{/other_user}","gists_url":"https://api.github.com/users/rauschma/gists{/gist_id}","starred_url":"https://api.github.com/users/rauschma/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rauschma/subscriptions","organizations_url":"https://api.github.com/users/rauschma/orgs","repos_url":"https://api.github.com/users/rauschma/repos","events_url":"https://api.github.com/users/rauschma/events{/privacy}","received_events_url":"https://api.github.com/users/rauschma/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":15,"created_at":"2015-12-02T00:38:40Z","updated_at":"2015-12-03T16:58:25Z","closed_at":null,"body":"Wondering: it seems like locking down what features are allowed for code pointed to by `jsnext:main` would be useful. Wouldn’t (e.g.) `es2015:main` be a better name? Otherwise, there is little that tools can rely on."},"comment":{"url":"https://api.github.com/repos/rollup/rollup/issues/comments/161715373","html_url":"https://github.com/rollup/rollup/issues/337#issuecomment-161715373","issue_url":"https://api.github.com/repos/rollup/rollup/issues/337","id":161715373,"user":{"login":"rauschma","id":526114,"avatar_url":"https://avatars.githubusercontent.com/u/526114?v=3","gravatar_id":"","url":"https://api.github.com/users/rauschma","html_url":"https://github.com/rauschma","followers_url":"https://api.github.com/users/rauschma/followers","following_url":"https://api.github.com/users/rauschma/following{/other_user}","gists_url":"https://api.github.com/users/rauschma/gists{/gist_id}","starred_url":"https://api.github.com/users/rauschma/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rauschma/subscriptions","organizations_url":"https://api.github.com/users/rauschma/orgs","repos_url":"https://api.github.com/users/rauschma/repos","events_url":"https://api.github.com/users/rauschma/events{/privacy}","received_events_url":"https://api.github.com/users/rauschma/received_events","type":"User","site_admin":false},"created_at":"2015-12-03T16:58:25Z","updated_at":"2015-12-03T16:58:25Z","body":"@Rich-Harris I mostly agree. However, a generic mechanism that can also support ECMAScript versions beyond ES6, later on, would be nice. Furthermore, I frequently write shell scripts in ES6 for Node.js. Having support for ES6 executables, eventually, would be great.\r\n\r\nHow about this?\r\n\r\n```js\r\n\"targets\": {\r\n  \"es2015\": {\r\n    main: ...,\r\n    bin: ...\r\n  }\r\n}\r\n```\r\n\r\nI’m not sure that would be much more work for package authors that are already using ES6 – they’d simply include both `src` and `build` directories. However, managing packages properly if any package can contain multiple targets will get more difficult."}}