{"action":"closed","issue":{"url":"https://api.github.com/repos/facebookincubator/create-react-app/issues/636","repository_url":"https://api.github.com/repos/facebookincubator/create-react-app","labels_url":"https://api.github.com/repos/facebookincubator/create-react-app/issues/636/labels{/name}","comments_url":"https://api.github.com/repos/facebookincubator/create-react-app/issues/636/comments","events_url":"https://api.github.com/repos/facebookincubator/create-react-app/issues/636/events","html_url":"https://github.com/facebookincubator/create-react-app/issues/636","id":176507693,"number":636,"title":"some pragmatic features","user":{"login":"ccorcos","id":1794527,"avatar_url":"https://avatars.githubusercontent.com/u/1794527?v=3","gravatar_id":"","url":"https://api.github.com/users/ccorcos","html_url":"https://github.com/ccorcos","followers_url":"https://api.github.com/users/ccorcos/followers","following_url":"https://api.github.com/users/ccorcos/following{/other_user}","gists_url":"https://api.github.com/users/ccorcos/gists{/gist_id}","starred_url":"https://api.github.com/users/ccorcos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ccorcos/subscriptions","organizations_url":"https://api.github.com/users/ccorcos/orgs","repos_url":"https://api.github.com/users/ccorcos/repos","events_url":"https://api.github.com/users/ccorcos/events{/privacy}","received_events_url":"https://api.github.com/users/ccorcos/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/facebookincubator/create-react-app/labels/discussion","name":"discussion","color":"fbca04"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-09-12T23:08:14Z","updated_at":"2016-09-13T13:50:19Z","closed_at":"2016-09-13T13:50:19Z","body":"Hey there, I'm considering dropping my existing build system in favor of `create-react-app`, but there are a few features that I would need. At some point, I'll likely need to fork, but until then, I'm curious if any of these features appeal to you enough to open up a PR.\r\n\r\n- absolute imports\r\n\r\nIn a large codebase, relative paths can get really annoying and make it hard to determine where files are being used. I'd like to suggest aliasing the project name to the root of the project. That way you can write something like `import Env from 'create-react-app/config/env'`. And if you want to find out where this file is used, its a simple find-all query for the file path.\r\n\r\n- babel-polyfill\r\n\r\nlooks like this project isnt using the [babel-polyfill](https://babeljs.io/docs/usage/polyfill/). any reason you opted to use a [variety of other polyfills](https://github.com/facebookincubator/create-react-app/blob/master/config/polyfills.js) instead? \r\n\r\n- stage-0 preset\r\n\r\nsimilarly, is the any reason this project is using [a bunch of babel plugins](https://github.com/facebookincubator/create-react-app/blob/master/config/babel.dev.js#L28-L47) rather than just using the stage-0 preset?\r\n\r\n- postcss variables / imports\r\n\r\nWhat is the preferred method of sharing CSS variables amongst files? My current solution is to `@import` a `variables.css` file that doesnt generate any css so long as autoprefixer is prefixing for a browser that doesnt support css variables. I'm not sure this is the best solution since eventually this will result in duplicate css once browsers support css variables. But I dont want to rely on magic globals either.\r\n\r\n- stylelint\r\n\r\nany interest in adding [stylelint](https://github.com/stylelint/stylelint) as a postcss plugin?\r\n\r\n- configurable environments / feature flags\r\n\r\nI'd like to be able to run the application from the cli specifying the NODE_ENV and/or feature flags that use the define plugin. Something like `NODE_ENV=\"replay\" npm start` which would let me start up the app in development mode with my replay devtool so I can run through various pre-recorded redux scenes.\r\n\r\n- deploy elsewhere\r\n\r\nWe're deploying our stuff to S3. Given this is a \"zero-config\" build tool, I'm not sure how adding an s3 deploy script would work.\r\n\r\n- how to build component library package?\r\n\r\nSuppose I have a bunch of shared React components. How would I build this package so that I can publish it on NPM and require it from another project? The fact that babel isnt parsing `node_modules` means that we need to build a distribution file. But we also shouldnt be minifying or hashing the filenames, and we also dont need an index.html file. Any ideas how we could outfit this tool to work for React component libraries?\r\n\r\n- zero-configuration (configurable) build tool\r\n\r\nthis all leads me to thinking that maybe the right way to go is to have a configurable build tool with some zero-configuration defaults. how to I set the eslint config, flowtype config, stylelint config, babel config? I dont want to rely on a `.babelrc` or something that I have to copy into all of my projects. Ideally, I could create a package called `chets-build-system` which depends on `create-react-app-core` and configures it with my custom configs. the `create-react-app` package can simply have a set of sane defaults but doesnt necessarily have all the feature I want...\r\n"}}
{"actor":{"display_login":"gaearon"}}