This message was deleted.
# helpdesks
steep-balloon-41261
10/02/2022, 9:56 AMThis message was deleted.
s
some-painter-46967
10/02/2022, 9:57 AMWelcome to Node.js v14.20.0.
or 18, there is no change
some-painter-46967
10/02/2022, 9:59 AMwhen I remove livekit-server-sdk from my project the problem disappears.
some-painter-46967
10/02/2022, 9:59 AM"dependencies": {
"core-js": "^3.8.3",
"crypto-browserify": "^3.12.0",
"livekit-client": "^1.4.1",
"livekit-server-sdk": "^1.0.2",
"stream-browserify": "^3.0.0",
"vue": "^2.6.14"
},
some-painter-46967
10/02/2022, 9:59 AMconst { defineConfig } = require('@vue/cli-service')
module.exports = defineConfig({
transpileDependencies: true,
configureWebpack: {
resolve: {
fallback: {
"stream": require.resolve("stream-browserify"),
"crypto": require.resolve("crypto-browserify")
},
},
}
})
some-painter-46967
10/02/2022, 9:59 AMThank you in advance
p
polite-kilobyte-67570
10/02/2022, 10:17 AMhi!
the
livekit-server-sdks
some-painter-46967
10/02/2022, 10:38 AMHmm.
I thought of it as a client that uses api's. this situation did not come to my mind. thank you.
p
polite-kilobyte-67570
10/02/2022, 10:41 AMhappy to help! just for context, there’s also a security concern: you should never provide your livekit api key and api secret to a client facing environment as those credentials might get stolen by a malicious actor.
that’s why all APIs requiring those credentials are supposed to only run in a secure server environment where users don’t have direct access to
👍 1
55 Views