Open marr opened 1 month ago
Name | Link |
---|---|
Latest commit | f4ec13bc6d7983909116f9c70a4e6834c1e00f47 |
Latest deploy log | https://app.netlify.com/sites/pinia-playground/deploys/667965097c907f0008210a0f |
Name | Link |
---|---|
Latest commit | f4ec13bc6d7983909116f9c70a4e6834c1e00f47 |
Latest deploy log | https://app.netlify.com/sites/pinia-official/deploys/66796509ee7b290008cdb9cb |
When using the pinia nuxt module with nuxt layers, there were some things that don't appear to work correctly.
I am trying to solve for a nuxt layer workflow, which adds the pinia module and registers some stores in the base layer. I want those stores to be available to my containing app, as well as stores that the containing app defines.
The issues I found with the current state of the module include:
I believe this PR solves those three problems. We remove some use of a deprecated API as well.
To add tests to this, I think I'd need to create a new "playground-layer" directory and extend from that in a new nuxt spec pertaining to layer functionality. If you agree with these changes, we can discuss if you'd like that as part of this.
Note: This may break nuxt 2 compatibility. I can try to add back support if this is a decent enough approach to fixing layer support.