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

Expose PARAGON_VERSION as a global variable via @edx/frontend-build so it's accessible via MFEs and JS libraries #2321

Open
Tracked by #144
adamstankiewicz opened this issue May 20, 2023 · 0 comments
Assignees

Comments

@adamstankiewicz
Copy link
Member

adamstankiewicz commented May 20, 2023

In order to access the Paragon version from the package-lock.json file (using package-lock.json because the specified version in package.json may not always be the one that is actually installed), we would need to expose a PARAGON_VERSION global variable via @edx/frontend-build such that @edx/frontend-platform has access to it.

Otherwise, I'm not sure of another way to get access to the package-lock.json file within a React application running the browser, which can't run node processes to parse the file system.

@adamstankiewicz adamstankiewicz self-assigned this May 20, 2023
@adamstankiewicz adamstankiewicz moved this from Backlog to In review in Paragon Working Group May 20, 2023
@adamstankiewicz adamstankiewicz changed the title Expose PARAGON_VERSION as a global variable via @edx/frontend-build so its accessible via MFEs Expose PARAGON_VERSION as a global variable via @edx/frontend-build so it's accessible via MFEs May 20, 2023
@adamstankiewicz adamstankiewicz changed the title Expose PARAGON_VERSION as a global variable via @edx/frontend-build so it's accessible via MFEs Expose PARAGON_VERSION as a global variable via @edx/frontend-build so it's accessible via MFEs and JS libraries May 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In review
Status: In review
Development

Successfully merging a pull request may close this issue.

1 participant