Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use spago for managing the server package set, attempt 2 #150

Merged
merged 1 commit into from
Apr 12, 2020

Conversation

hdgarrood
Copy link
Collaborator

Like #148, except we keep the same set of dependencies.

Comment on lines +34 to +35
, "react"
, "react-dom"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this mainly for testing the shim stuff? Do we intend to have a process for adding additional libraries from the set. Or perhaps we should just blanket state we are not adding more libraries until we figure out a caching/purging solution for externs?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I originally added these a week or two ago for testing the shim stuff, yeah. I'd like to at least add back libraries which were previously provided by other backends (#142). After that, saying we are not going to add any more libraries until we figure out a caching/purging solution (at which point we can add the whole package set) works for me.

@hdgarrood hdgarrood merged commit 4341a0d into master Apr 12, 2020
@hdgarrood hdgarrood deleted the spago-server-package-set-2 branch April 12, 2020 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants