This is not a issue. Gatsby works pretty smooth. Has great documentation. I am requesting a feature or I would want to work with Gatsby to get a support for Angular. People/community building their apps on angular are missing out or could use these on these powerful and clean interfaces that Gatsby provides for react ecosystem.
As discussed on twitter, https://twitter.com/gatsbyjs/status/952745191923789825 I would love to get the discussion started here. I would love to contribute but I will need help in understanding how I can go about.
you would probably need a whole rewrite of gatsby.. the only thing remaining from gatsby would be the name. i understand the appeal for angular devs but I don't think this is really feasible
Angular and react on higher level offer somewhat similar interfaces/life cycle hooks. @akadop trying to understand what parts of Gatsby are really hard to make it work for other frameworks?
Hey! Thanks for dropping by @suhasdeshpande :-)
So definitely thought about supporting Angular, Vue, Glimmer, etc. with Gatsby. It's definitely possible. Basically where we directly do React things, we'd need to create abstractions so we could choose between different frameworks. Most of the direct React actions happens in files in https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby/cache-dir
This would also cause problems with plugins which implement gatsby-browser.js & gatsby-ssr.js as many of them add React components to sites. Either you duplicate those for angular/ember/vue equivalents or there's some way of easily choosing the specific framework version that's needed e.g. gatsby-browser-angular.js.
Many parts of Gatsby wouldn't change e.g. the GraphQL data layer, webpack/babel setup, and the other node-specific APIs.
This would be a major undertaking β once which I'm not going to jump on any time soon. I don't think we could do this unless there parties from at least two other frameworks that were willing to commit serious time to refactoring parts of Gatsby and building out support for their framework-of-choice.
Thanks, @KyleAMathews for the technical explanation
Very interesting chat. Really appreciate that you guys are open to other render engines. We are in the same scenario, trying to move the whole company to use React instead of Angular is almost impossible in a short deadline
Angular is a huge project with lots of dependencies and React is just a simple render library. I think we will need to wait for the development of Angular Elements that @robwormald proposes in his repo https://github.com/robwormald/angular-elements (now moved to a branch in angular repo https://github.com/angular/angular/tree/labs/elements by @gkalpak)
The time has come for integration. Angular Team and @robwormald have released Angular 6 which includes the aforementioned Angular Elements. This should make for easier path to including Gatsby within Angular applications. Maybe without even reworking the React parts.
Is anyone working on the Gatsby Angular Integration?
Hi everyone I am searching how we can use gatsby inside specific folder of an angular app and google lands me here @KyleAMathews Thanks for the technical description but after lots of research and google I am still not able to figure it out how we can combine this wonderful frameworks. anyone with any kind of success ?
Hiya!
This issue has gone quiet. Spooky quiet. π»
We get a lot of issues, so we currently close issues after 30 days of inactivity. Itβs been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
Thanks for being a part of the Gatsby community! πͺπ
I'm actually fine closing it.
Awwww, I was looking forward to 1st class support for Angular ):
Are there any alternatives for angular?
Are there any alternatives for angular?
Angular has something similar in the form of Angular Universal, There is currenly first class support for Server Side Rendering (SSR). First class support for prerendering (Static site) is coming soon.
In the mean time, you can use something like angular-prerender for static site generation.
Thanks
Most helpful comment
Hey! Thanks for dropping by @suhasdeshpande :-)
So definitely thought about supporting Angular, Vue, Glimmer, etc. with Gatsby. It's definitely possible. Basically where we directly do React things, we'd need to create abstractions so we could choose between different frameworks. Most of the direct React actions happens in files in https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby/cache-dir
This would also cause problems with plugins which implement gatsby-browser.js & gatsby-ssr.js as many of them add React components to sites. Either you duplicate those for angular/ember/vue equivalents or there's some way of easily choosing the specific framework version that's needed e.g. gatsby-browser-angular.js.
Many parts of Gatsby wouldn't change e.g. the GraphQL data layer, webpack/babel setup, and the other node-specific APIs.
This would be a major undertaking β once which I'm not going to jump on any time soon. I don't think we could do this unless there parties from at least two other frameworks that were willing to commit serious time to refactoring parts of Gatsby and building out support for their framework-of-choice.