Skip to content

Conversation

@nd2024
Copy link
Contributor

@nd2024 nd2024 commented May 7, 2024

Got this error below when using this module. I fix it by importing useRuntimeConfig inside isBanExpired.

"useRuntimeConfig is not defined"
at isBanExpired (D:\2024-2025\Projects\mn-v3-microservices\Frontend\[PROJECT]\node_modules\nuxt-api-shield\dist\runtime\server\utils\isBanExpired.mjs:2:19)
at Object.handler (D:\2024-2025\Projects\mn-v3-microservices\Frontend\[PROJECT]\node_modules\nuxt-api-shield\dist\runtime\server\middleware\shield.mjs:24:7)
at async /D:/2024-2025/Projects/mn-v3-microservices/Frontend/[PROJECT]/node_modules/h3/dist/index.mjs:1962:19
at async Object.callAsync (/D:/2024-2025/Projects/mn-v3-microservices/Frontend/[PROJECT]/node_modules/unctx/dist/index.mjs:72:16)
at async Server.toNodeHandle (/D:/2024-2025/Projects/mn-v3-microservices/Frontend/[PROJECT]/node_modules/h3/dist/index.mjs:2249:7)

#9

-- fix useRuntimeConfig is not defined
@rrd108
Copy link
Owner

rrd108 commented May 7, 2024

Thank you for the PR, but before I merge it I would need a reproduction link, or code or something to see why it happens to some users.

Can you provide something?

@rrd108 rrd108 merged commit 014edfe into rrd108:main May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants