You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 31, 2024. It is now read-only.
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 Vulcan Accounts 2.0 #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
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: