Open rhtenhove opened 6 months ago
For internal tracking, this was first reported: https://linear.app/netlify/issue/FRP-985/ and has been fixed as of: https://linear.app/netlify/issue/FRP-959/.
The only difference is that, there getStore
was being called during build time and here, based on the stack trace, this looks to be happening within a Function. I don't think the fix was for that part.
What's the use-case here? Any particular reason to call getStore
outside of the default export?
I came here due to the report: https://answers.netlify.com/t/107958/11
Describe the bug
When using for example:
Outside a function,
netlify dev
is fine with it and will store and retrieve stuff as expected. However when using this in production (or a deploy preview), the following error is thrown.To fix this,
getStore
needs to happen within a function called by a request.Configuration