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

Document "top-level" bootstrapping #439

Open
TheMcMurder opened this issue Apr 16, 2021 · 0 comments
Open

Document "top-level" bootstrapping #439

TheMcMurder opened this issue Apr 16, 2021 · 0 comments

Comments

@TheMcMurder
Copy link
Contributor

TheMcMurder commented Apr 16, 2021

I've noticed a number of questions about boostrapping 3rd party scripts like split or authorization. I generally respond with a discussion about single-spa utilities, but I realized recently that we're not discussing anywhere in the docs I could find how to initialize/bootstrap those types of dependencies.

I'm thinking about it is the pattern we used at Canopy around having the single-spa root config handle top level bootrapping for things like Sentry, feature toggles, Auth, etc. IIRC we called it spa-boostrapper or something like that.

Is this a pattern we want to encourage or is there a better approach we'd like to suggest?

If we want to encourage this pattern we should probably also update the docs around root-config so that we call out that it's a place to put top level bootstrapping.

@TheMcMurder TheMcMurder changed the title Document application bootstrap dependencies Document "top-level" bootstrapping Apr 16, 2021
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

No branches or pull requests

1 participant