An issue to track our progress in using Vulcan client side tooling in other Node frameworks, like Next, Gatsby, React Native etc.
This means GraphQL client, but also JS components like the SmartForm and Datatable.
This issue only concerns client side code, so an existing Vulcan backend can be consumed by any kind of js application. It does not concern server side code, which is still a bit more dependant on Meteor (Mongo collection system and a few other specific setups).
Steps:
[ ] demeteorize client side code. It's almost done, only blocker is https://github.com/VulcanJS/Vulcan/issues/1896. A few references to Meteor will have to be changed elsewhere too, eg in the Apollo client.
[ ] allow distant connection to the graphql server with CORS setup
[ ] allow to build Vulcan code with Webpack, at least for client. Storybook was a first step toward this, since we can already build most components correctly
[ ] create a Lerna monorepo and publish packages on npm
eric-burel
commented
4 years ago
An issue to track our progress in using Vulcan client side tooling in other Node frameworks, like Next, Gatsby, React Native etc. This means GraphQL client, but also JS components like the SmartForm and Datatable.
This issue only concerns client side code, so an existing Vulcan backend can be consumed by any kind of js application. It does not concern server side code, which is still a bit more dependant on Meteor (Mongo collection system and a few other specific setups).
Steps: