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
I'm curious if there's a way we could make Vuex easily available for figgy, but not necessarily include it in the default lux export. I ran into an issue when adding lux to the departmental blog (which doesn't actually need Vuex). Vuex errored because it thought it was in a node enviornment rather than a browser, so we needed to trick it in order to use Lux.
@sandbergja yes, I have been having issues with the Gallery component in Figgy. I had to migrate the Gallery component to the local Figgy code to get it to work as it won't work from the NPM package.
I am wondering if we simply don't do any state management in LUX? 🤔
Expected behavior
When the following command is run on figgy, a build without errors is expected:
Actual behavior
The build fails with this error message:
Steps to replicate
Checkout the
figgy/6294-vue-lux-upgrade
branch and runbin/vite build --clear --mode=development
Impact of this bug
We are unable to upgrade Figgy to the latest version of LUX since it uses the gallery Vuex module.
Implementation notes, if any
Lux may need an export statement, like this:
https://github.com/pulibrary/lux-design-system/blob/main/src/index.js#L22
The text was updated successfully, but these errors were encountered: