You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
In order to access the Paragon version from the
package-lock.json
file (usingpackage-lock.json
because the specified version inpackage.json
may not always be the one that is actually installed), we would need to expose aPARAGON_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.The text was updated successfully, but these errors were encountered: