fix: example app render plugins and remove LMS authentication #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The host example app was not able to render the plugins defined in
env.config.js
due to something to do with thefrontend-component-header
andfrontend-component-footer
dependencies living in the host's package.json (introduced in #61).Although the reason is unclear of how they affected the configuration, we can safely remove them as they were unused by both example apps.
In addition, the
hydrateAuthenticatedUser
in Initialize is set tofalse
so that the LMS isn't required to run the example apps, which will allow more from the open-source community to easily access the examples.Steps to test (following steps in README for developers):
make requirements
in rootnpm run start:example
localhost:8080
to see host app with direct and iFrame plugins