-
Notifications
You must be signed in to change notification settings - Fork 243
Who's using it and where? #437
Comments
Where: My own blog -> ainoob.com What did I changed?
|
We (ueno.) have a modified version, which we currently use to start all of our universal projects. You can see some of our clients at https://ueno.co - most (if not all) are built with react, some of them use the starter. |
This is awesome, thanks for opening this @oyeanuj I'm more than happy to link this off via the readme/docs. 👍 |
I'm using in projects for Seek. |
As per @ctrlplusb’s comment here: ctrlplusb#437 (comment) 98854669
* Update Webpack version * Update Webpack version * Fix acronym * Fix markdown formatting. * Update that redux branch does not have Flow * Add 'Who is using it' section in the README As per @ctrlplusb’s comment here: #437 (comment) 98854669
* Update Webpack version * Update Webpack version * Fix acronym * Fix markdown formatting. * Update that redux branch does not have Flow * Add 'Who is using it' section in the README As per @ctrlplusb’s comment here: ctrlplusb#437 (comment) 98854669
* Minor readme updates (#501) * Update Webpack version * Update Webpack version * Fix acronym * Fix markdown formatting. * Update that redux branch does not have Flow * Add 'Who is using it' section in the README As per @ctrlplusb’s comment here: #437 (comment) 98854669 * Server logging enhancements (#508) * Improving logging experience + consolidating to single log function * Adding pretty-error for more readable node error stack * Fix eslint error * Logging requests received * Re-commit logging requests received * Replacing colors with chalk
* Minor readme updates (#501) * Update Webpack version * Update Webpack version * Fix acronym * Fix markdown formatting. * Update that redux branch does not have Flow * Add 'Who is using it' section in the README As per @ctrlplusb’s comment here: #437 (comment) 98854669 * Server logging enhancements (#508) * Improving logging experience + consolidating to single log function * Adding pretty-error for more readable node error stack * Fix eslint error * Logging requests received * Re-commit logging requests received * Replacing colors with chalk
* Update Webpack version * Update Webpack version * Fix acronym * Fix markdown formatting. * Update that redux branch does not have Flow * Add 'Who is using it' section in the README As per @ctrlplusb’s comment here: ctrlplusb/react-universally#437 (comment) 98854669
I am using it to rebuild my page since it did not have SEO, the problem is that I can not use scss, I do not understand how to install it, can you help me? |
Hey @CamilaSolis, you can try the postcss branch that has scss inside. Any help you need, sens us a message |
We're using React universally as the boilerplate on all our project work at the moment. Other projects we have running on React universally are: a sustainability auditing tool; a sustainability audit forecasting tool; and a small site to remind you to Make Better Software Fave stack at the moment is the Sass build with Apollo GraphQL client. |
Hey folks, inspired from some of the repos, I was curious to see if there is any interest in having this sticky issue to see who all are using react-universally. This can also be added to the Readme if @ctrlplusb feels good about it.
I see it as being useful (and inspires confidence in) to both newcomers and authors alike, to know this information. So for folks who are using (or planning to use) this excellent starter kit -
PS. @ctrlplusb Feel free to close this issue if doesn't feel helpful.
The text was updated successfully, but these errors were encountered: