Skip to content
This repository was archived by the owner on Feb 18, 2021. It is now read-only.

Split client and server into independent packages - #174

Merged
Mor Shemesh (morsh) merged 6 commits into
ibex-version-1.0from
fortis-ibex
Jun 29, 2017
Merged

Split client and server into independent packages#174
Mor Shemesh (morsh) merged 6 commits into
ibex-version-1.0from
fortis-ibex

Conversation

@c-w

@c-w Clemens Wolff (c-w) commented Jun 15, 2017

Copy link
Copy Markdown
Contributor

This pull request makes the server and client packages independently deployable and runnable. This makes the developer story slightly worse (we now have to run two servers in separate shells, see updates in readme), but it gives us a number of benefits, including:

  • Better long-term maintainability by increasing the logical separation between client and server.
  • Option to have client and server depend on different versions of the same package. This is a requirement for using GraphQL+Apollo since the Apollo React client and the Apollo Express server rely on different versions of the Apollo core library.
  • Ability to publish client and server as independent npm modules, e.g. to deploy them to separate webapps or to include them selectively in third-party pages.

This pull request is a necessary pre-condition for a potential Fortis/Ibex integration, but has value on its own for the reasons mentioned above. As such, I propose to merge this pull request before we start the Fortis/Ibex integration.

Previously Travis auto-installed yarn for us because we had a yarn.lock
file in the repository root -- now we no longer have this so we have to
manually set it up.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants