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
2021-10-31T17:37:11.535Z 5180479b-60c6-4715-9a89-4ae3d59f27ad ERROR /var/task/node_modules/security-context/js/index.js:1
Error: ENOENT: no such file or directory, open '/var/task/node_modules/security-context/contexts/security-v1.jsonld'
at Object.openSync (fs.js:498:3)
at Proxy.readFileSync (fs.js:394:35)
at _read (/var/task/node_modules/security-context/js/index.js:12:8)
at Object.<anonymous> (/var/task/node_modules/security-context/js/index.js:19:3)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10) {
errno: -2,
syscall: 'open',
code: 'ENOENT',
path: '/var/task/node_modules/security-context/contexts/security-v1.jsonld'
}
RequestId: 5180479b-60c6-4715-9a89-4ae3d59f27ad Error: Runtime exited with error: exit status 1
Runtime.ExitError
It would be wiser to use require, or import instead of fs.
This prevents these libraries from working in environments where the fs / modules may not be accessible, such as cloud functions on vercel / next.js or React Native....
In turn this error causes failures in any other dependencies that rely of security context.
The text was updated successfully, but these errors were encountered:
Probably caused by the use of fs and path here: https://github.com/w3c-ccg/security-vocab/blob/main/js/index.js
It would be wiser to use require, or import instead of fs.
This prevents these libraries from working in environments where the fs / modules may not be accessible, such as cloud functions on vercel / next.js or React Native....
In turn this error causes failures in any other dependencies that rely of security context.
The text was updated successfully, but these errors were encountered: