{"action":"created","issue":{"url":"https://api.github.com/repos/davidtheclark/cosmiconfig/issues/109","repository_url":"https://api.github.com/repos/davidtheclark/cosmiconfig","labels_url":"https://api.github.com/repos/davidtheclark/cosmiconfig/issues/109/labels{/name}","comments_url":"https://api.github.com/repos/davidtheclark/cosmiconfig/issues/109/comments","events_url":"https://api.github.com/repos/davidtheclark/cosmiconfig/issues/109/events","html_url":"https://github.com/davidtheclark/cosmiconfig/issues/109","id":297253508,"number":109,"title":"Load an ES2015 module config file ","user":{"login":"danawoodman","id":157695,"avatar_url":"https://avatars1.githubusercontent.com/u/157695?v=4","gravatar_id":"","url":"https://api.github.com/users/danawoodman","html_url":"https://github.com/danawoodman","followers_url":"https://api.github.com/users/danawoodman/followers","following_url":"https://api.github.com/users/danawoodman/following{/other_user}","gists_url":"https://api.github.com/users/danawoodman/gists{/gist_id}","starred_url":"https://api.github.com/users/danawoodman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danawoodman/subscriptions","organizations_url":"https://api.github.com/users/danawoodman/orgs","repos_url":"https://api.github.com/users/danawoodman/repos","events_url":"https://api.github.com/users/danawoodman/events{/privacy}","received_events_url":"https://api.github.com/users/danawoodman/received_events","type":"User","site_admin":false},"labels":[{"id":283630826,"url":"https://api.github.com/repos/davidtheclark/cosmiconfig/labels/help%20wanted","name":"help wanted","color":"159818","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":41,"created_at":"2018-02-14T21:35:35Z","updated_at":"2018-03-16T16:43:03Z","closed_at":null,"author_association":"NONE","body":"I am writing a CLI tool where I want my end users to be able to write their config file in ES6/7/Next, how can I accomplish this?\r\n\r\nEg, my `foo.config.js` file:\r\n```js\r\nimport foo from './foo'\r\n\r\nexport default {  foo, someOtherOption: true }\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/davidtheclark/cosmiconfig/issues/comments/373773240","html_url":"https://github.com/davidtheclark/cosmiconfig/issues/109#issuecomment-373773240","issue_url":"https://api.github.com/repos/davidtheclark/cosmiconfig/issues/109","id":373773240,"user":{"login":"chrisblossom","id":1595871,"avatar_url":"https://avatars3.githubusercontent.com/u/1595871?v=4","gravatar_id":"","url":"https://api.github.com/users/chrisblossom","html_url":"https://github.com/chrisblossom","followers_url":"https://api.github.com/users/chrisblossom/followers","following_url":"https://api.github.com/users/chrisblossom/following{/other_user}","gists_url":"https://api.github.com/users/chrisblossom/gists{/gist_id}","starred_url":"https://api.github.com/users/chrisblossom/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chrisblossom/subscriptions","organizations_url":"https://api.github.com/users/chrisblossom/orgs","repos_url":"https://api.github.com/users/chrisblossom/repos","events_url":"https://api.github.com/users/chrisblossom/events{/privacy}","received_events_url":"https://api.github.com/users/chrisblossom/received_events","type":"User","site_admin":false},"created_at":"2018-03-16T16:43:03Z","updated_at":"2018-03-16T16:43:03Z","author_association":"CONTRIBUTOR","body":"@jdalton I personally don't care about the dependency size, just was pointing out why others might object. Although I do think it adds complexity that could be offloaded to the consumer if they want to support ES Modules via ``esm`` using a custom JS-parsing function. Also, if the user decides to use ``babel``, will ``esm`` have any conflicts/issues?\r\n\r\nUse case for a custom JS-parsing function is so you wouldn't be forced to use ``babel-register``, because it does have negative issues (my use case, I don't want to use ``babel-register`` if at all possible, otherwise I'll need to figure out how to run ``cosmiconfig`` in a separate node ``spawn`` instance). Or they could support just es2015 modules with ``esm`` with a custom JS-parsing function. Or as said earlier, could use a ``typescript`` parser or some other parser that hasn't been released yet. The user could revert back to ``require-from-string`` if they wanted to as well with the custom parsing function.\r\n\r\nI've read in other issues you want to keep this library as \"low level\" as possible, which I agree with. To me a custom JS-parsing function goes along with that idea."}}
{"actor":{"display_login":"chrisblossom"}}