When I use gulp_jspm I get this DeprecationWarning is there something else I should use to create my bundle files? When I used gulp-jspm-build I have to add some node files that I never had to do before.
Should I use gulp-jspm-build'?
Current versions:
node: v6.9.5
ts: 2.7.2
.pipe(gulp_jspm({
selfExecutingBundle: true
}),true)
(node:25936) [DEP0097] DeprecationWarning: Using a domain property in MakeCallback is deprecated. Use the async_context variant of MakeCallback or the AsyncResource class instead. (Triggered by calling processImmediate on process.)
(Use node --trace-deprecation ... to show where the warning was created)
According to the author of gulp-jspm, it has not been updated or maintained since 2017.
https://github.com/brillout/gulp-jspm/issues/45
Related
I am trying to create a sample nodejs app for kafkajs producer and consumer. When I start the app, I get the deprecation error. So, I tried with --trace-deprecation flag and get this stack trace. How can I fix it? I tried using different versions of kafkajs, but still keep getting this error
(node:61452) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
at Object.connect (node:_tls_wrap:1670:15)
at /BitBucketRepos/node-js/SimpleProducerConsumer/node_modules/kafkajs/src/network/socketFactory.js:12:13
at module.exports (/BitBucketRepos/node-js/SimpleProducerConsumer/node_modules/kafkajs/src/network/socket.js:24:18)
at /BitBucketRepos/node-js/SimpleProducerConsumer/node_modules/kafkajs/src/network/connection.js:240:23
at new Promise (<anonymous>)
at Connection.connect (/BitBucketRepos/node-js/SimpleProducerConsumer/node_modules/kafkajs/src/network/connection.js:167:12)
at ConnectionPool.getConnection (/BitBucketRepos/node-js/SimpleProducerConsumer/node_modules/kafkajs/src/network/connectionPool.js:56:24)
at Broker.connect (/BitBucketRepos/node-js/SimpleProducerConsumer/node_modules/kafkajs/src/broker/index.js:86:52)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /BitBucketRepos/node-js/SimpleProducerConsumer/node_modules/kafkajs/src/cluster/brokerPool.js:319:9
I have tried with using ksfkajs version 1.15.0, 1.16.0, 2.1.0 in package.json - but keep getting the same error.
How can I eliminate this warning?
Thank you
Upgrade your NodeJS version should resolve this
https://techiedan.com/nodejs-ip-address-is-not-permitted-by-rfc-6066/
Upgrade your NodeJS version into the newest stable release. At time of writing, this is at version 15 which should resolve this issue as I believe the IP address is now ignored in future version.
I'm trying to build a tool that requires the user to load a node bundle JS file during runtime and evaluate some of the exported functions.
Currently on the local Dev environment this works fine using (do note path is a user path)
delete require.cache[path];
let inst = await import(path);
if (!inst.default) {
console.warn(`Unable to load core from ${path}`)
return false;
}
But once packaged I'm getting the following error,
[112207:0221/164632.255945:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
16:46:32.350 › Checking for update
16:46:35.212 › Update for version 4.5.0 is not available (latest version: 4.5.0, downgrade is disallowed).
16:46:35.213 › checkForUpdatesAndNotify called, downloadPromise is null
(node:112169) UnhandledPromiseRejectionWarning: Error: Cannot find module '/home/ukr/Documents/work/<file>.js'
at t (/tmp/.mount_GradieAhn7PR/resources/app.asar/dist/main/main.js:2:536067)
at /tmp/.mount_GradieAhn7PR/resources/app.asar/dist/main/main.js:2:519883
at IpcMainImpl.<anonymous> (/tmp/.mount_GradieAhn7PR/resources/app.asar/dist/main/main.js:2:519841)
(Use `electron-react-boilerplate --trace-warnings ...` to show where the warning was created)
(node:112169) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
^C^C
This is a quick internal devtool and requires no dependency loading nor security. How can I archive this? Thanks in advance!
I've got a problem in my NestJs app. Project was running perfect until yesterday.
Apparently my node.js upgraded from 14.16.1 to 14.17.0. So I changed this version number in my engines object, in package.json. I executed yarn install again, to make sure everything was there, and tried yarn start:dev (which translates to nest start --watch).
But my app isn't running =(
It seems like there's something wrong regarding my apollo-server-fastify:
UnhandledPromiseRejectionWarning: Error: You must `await server.start()` before calling `server.createHandler()`
at ApolloServer.assertStarted (/app/node_modules/apollo-server-fastify/node_modules/apollo-server-core/dist/ApolloServer.js:213:19)
at ApolloServer.createHandler (/app/node_modules/apollo-server-fastify/dist/ApolloServer.js:22:14)
at GraphQLModule.<anonymous> (/app/node_modules/#nestjs/graphql/dist/graphql.module.js:150:45)
at Generator.next (<anonymous>)
at /app/node_modules/tslib/tslib.js:117:75
at new Promise (<anonymous>)
at Object.__awaiter (/app/node_modules/tslib/tslib.js:113:16)
at GraphQLModule.registerFastify (/app/node_modules/#nestjs/graphql/dist/graphql.module.js:143:24)
at GraphQLModule.<anonymous> (/app/node_modules/#nestjs/graphql/dist/graphql.module.js:118:28)
at Generator.next (<anonymous>)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:323734) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:323734) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
I know apollo and fastify aren't the best friends right now, I've faced an issue in the past where I needed to downgrade some package, I guess. Does anyone knows how to debug/fix this? I feel clueless.
Current package versions:
"#nestjs/common": "^7.0.0",
"#nestjs/graphql": "^7.7.0",
"#nestjs/platform-fastify": "^7.6.4",
"apollo-server-fastify": "^3.0.0-alpha.3",
"graphql": "^15.5.0",
(I've also tried to upgrade apollo-server-fastify to alpha 4, but the problem persists).
TLDR
A temporary fix, until this issue is addressed by maintainers, is to copy this patch file into your repository, then modify your package.json to use the following:
"#nestjs/graphql": "patch:#nestjs/graphql#7.10.6#[YOUR/LOCAL/PATH]/graphql.patch"
Background
I ran into this same issue with my project. I'm not sure about the origin, but I did see that apollo-server-fastify was updated to 3.0.0-lambda.0 about 5 days ago and to 3.0.0-preview.0 a few hours ago.
I tracked the possible fix down to the registerFastify method in #nestjs/graphql. The solution, I believe, is to call await apolloServer.start() on line 228 in lib/graphql.module.ts before the Apollo Server's createHandler() method is called. I opened an issue on the repository with more details, which you can follow until resolved.
I implemented the fix in the template repository I'm working on with yarn patch #nestjs/graphql. The repository is available on the dev-nx branch at troncali/nest-vue. The patch is located in ./.yarn/patches/#nestjs/graphql.patch.
I migrated my app from angular 10 to 11, and updated to webpack 5 using :
"resolutions": {
"webpack": "^5.0.0"
}
When I ng build/serve I got the following warning =
(node:3926) [DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET_INDEXER] DeprecationWarning: chunk.files was changed from Array to Set (indexing Array is deprecated)
(Use `node --trace-deprecation ...` to show where the warning was created)
Any idea of what should I do? replace all Array by Set? and where can I put this node --trace-deprecation in my app in order to know what file cause this problem?
Thank you.
UPDATE
I added --trace-deprecation during build and got the following logs :
(node:12987) [DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET_INDEXER] DeprecationWarning: chunk.files was changed from Array to Set (indexing Array is deprecated)
at Set.fn (/Users/xxxxx/node_modules/webpack/lib/util/deprecation.js:128:4)
at xxx/node_modules/#angular-devkit/build-angular/src/webpack/plugins/analytics.js:173:57
at Array.forEach (<anonymous>)
at NgBuildAnalyticsPlugin._collectBundleStats (/xxxx/node_modules/#angular-devkit/build-angular/src/webpack/plugins/analytics.js:172:14)
at NgBuildAnalyticsPlugin._done (/xxx/node_modules/#angular-devkit/build-angular/src/webpack/plugins/analytics.js:242:14)
at Hook.eval [as callAsync] (eval at create (/xxx/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:14:1)
at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/xxx/node_modules/tapable/lib/Hook.js:18:14)
at /xxx/node_modules/webpack/lib/Compiler.js:468:23
at Compiler.emitRecords (/xxx/node_modules/webpack/lib/Compiler.js:846:39)
at /xxx/node_modules/webpack/lib/Compiler.js:460:11
Currently, Angular 11 with Webpack 5 is still experimental and work with Yarn only as mentioned here. So you may see some warning and errors here and there. I believe it is better to avoid production builds with it for now.
Most probably that it will be offically supported by Angular 12. You can see here that #angular-devkit/build-optimizer library will be supporting Webpack 5 in version 12.
What is meant by this?
(node:52213) Warning: Accessing non-existent property 'MongoError' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:52213) DeprecationWarning: Listening to events on the Db class has been deprecated and will be removed in the next major version.
You can just ignore this warning for now,
look at this answer by Lauren_Schaefer which is a MongoDB Employee.
Link for the answer from the mongoDB developers community is here:
https://developer.mongodb.com/community/forums/t/warning-accessing-non-existent-property-mongoerror-of-module-exports-inside-circular-dependency/15411/6