Development – Developer OneNote

In Kusto Query Language (KQL), you can’t directly get the count of each column in a single command. However, you can get the count of each column one by one using the count() function. Here’s an example: Replace ‘datatable’ with your table name and ‘Column1’, ‘Column2’, ‘Column3’ with your column names. This will give you the count…

Configure import order in a Next.js project

Jan 19, 2024

—

by

devonenote

in Development

To configure import order in a Next.js project, you can use ESLint with the “sort-imports” or “import/order” rules from the “eslint-plugin-import” plugin. Here’s how you can set it up: Install ESLint and the necessary plugins if you haven’t already Then, create a .eslintrc.json file in your project root if it doesn’t exist already. If it…

Solving the “/app/.next/standalone not found” Error in Next.js

Nov 30, 2023

—

by

devonenote

in Development

While building your Nextjs application within Docker, you may encounter the following error if you’re using the Docker sample from the official Nextjs GitHub site: This blog post offers a straightforward solution to this problem. Understanding the Error Understanding the Error The error message suggests that the system couldn’t compute the cache key as it…

Resolve Vercel deploy Error: Found invalid Node.js Version: “>=20.9.0”.

Nov 26, 2023

—

by

devonenote

in Development

If you’re deploying an application on Vercel and encounter the following error: Error: Found invalid Node.js Version: “>=20.9.0”. Please set “engines”: { “node”: “18.x” } in your package.json file to use Node.js 18. There’s no need to downgrade your application to Node.js 18. Here’s how you can fix the issue without downgrading: Your new deployment should successfully…

Solving the Angular Update Error: Conflicting peer dependency

Sep 9, 2023

—

by

devonenote

in Development

If you’re struggling to update your Angular version and encounter the following error when executing the command ‘npm install’: Here’s a potential solution: Delete the ‘node_modules’ folder and the ‘package-lock.json’ file, then reinstall npm. This could resolve your issue. To do this, execute the following commands:

Category: Development