Skip to main content

Blog Archive

Every post on Dewiride Developer Blogs, newest first. Pick a year or a month to narrow it down, or page through them all.

Posts
1,085
Topics
132
Reading time
130 h
First post
Jun 2025

Posts 151–180 of 1,085 · November 10–11, 2026

Page 6 of 37

November 2026

802 posts

Wednesday, November 11, 2026

16 of 27 posts

  1. How to Read Environment Variables at Runtime in Next.js

    A Next.js page that reads process.env can be built ahead of time and keep the value from the build forever. Await connection() inside Suspense to read the value from the running server — shown with one build started with a different value, in Next.js 16.4.6 with Cache Components.

  2. How to Validate Environment Variables When a Next.js App Starts

    Describe your Next.js app's settings with a zod schema, check them in instrumentation.ts when the server starts, and see the real results: next dev stops with a message per setting, next start answers every request with 500 until the setting is fixed, and next build isn't affected.

  3. How to Keep Server-Only Code Out of the Browser in Next.js

    Mark a module with import "server-only" so a Next.js build fails the moment a Client Component imports it, see the real error and the code that ships to the browser without it, and pass only safe values to Client Components — with Next.js 16.4.6.

  4. How to Commit a .env.example File in a Next.js Project

    A new Next.js app's .gitignore ignores every file that starts with .env, including .env.example. Add one !.env.example line, check it with git check-ignore -v, and commit the example while .env.local stays private.

  5. How to Pin Exact npm Package Versions

    npm saves version ranges such as ^4.6.7 by default. Turn on save-exact for a project with npm config set save-exact=true --location=project, pin new and existing packages, and use --save-exact for a single install — with real output from npm 12.2.3.

  6. How to Update npm to the Newest Version

    Check which npm you have, see the newest release and whether your Node.js supports it, and update with npm install -g npm@latest — with real output from Node.js 26.13.1 moving from npm 11.20.0 to npm 12.2.3.

  7. Fixed: "signal is aborted without reason" After Stopping an AG-UI Run

    In a React chat page built with @ag-ui/client 1.0.5, pressing Stop showed signal is aborted without reason as an error. abortRun ends the run with the client's own RUN_ERROR event, code abort; skipping that code in onRunErrorEvent fixed it.

  8. Fixed: next dev "Generated AGENTS.md for AI agents" in a Next.js App

    Running npm run dev from an AI coding assistant made Next.js 16.4.6 print Generated AGENTS.md for AI agents and add an AGENTS.md file, although the app was created with --no-agents-md. It is the agentRules option; agentRules false in next.config.ts removes the file.

  9. Fixed: Biome "Alternative text title element cannot be empty" in a New Next.js App

    After updating Biome to 2.6.8 in a new Next.js 16.4.6 app, biome check reported lint/a11y/noSvgWithoutTitle on all five sample SVG files in public. Biome 2.5 started checking .svg files; titles on the SVGs you use and deleting the ones you don't made the check clean.

  10. Fixed: Biome "The configuration schema version does not match the CLI version"

    After updating Biome from 2.4.2 to 2.6.8 in a new Next.js app, biome check said the configuration schema version does not match the CLI version and that the recommended field is deprecated. biome migrate --write updated biome.json in one step.

  11. Fixed: "npm warn deprecated eslint@9.39.5: This version is no longer supported" in a New Next.js App

    create-next-app 16.4.6 with ESLint installs eslint 9.39.5, which reached end of life in August 2026. Updating to ESLint 10.14.0 removes the warning; two scoped overrides bring npm audit back to zero, and three plugins still list only ESLint 9.

  12. Fixed: npm audit Reports "7 moderate severity vulnerabilities" in a New Next.js App

    A brand-new Next.js 16.4.6 app with ESLint reported 7 moderate severity vulnerabilities, and npm audit fix changed nothing. All seven came from one minimatch advisory, GHSA-g3hv-75wg-m249, inside typescript-eslint. A scoped npm override fixed it.

  13. Fixed: "typescript-eslint does not support TS 7.0." in a Next.js App

    After updating a new Next.js app to TypeScript 7.0.2, npm run lint stopped with typescript-eslint does not support TS 7.0. TypeScript 7.0 ships without a compiler API; the fix the TypeScript team recommends is two npm aliases that run TypeScript 6's API next to TypeScript 7's tsc.

  14. Fixed: "The application path is not writable, please check folder permissions and try again." in create-next-app

    create-next-app refused to create my Next.js app in web/agent-chat-ui and blamed folder permissions. The permissions were fine: the parent folder, web, didn't exist yet. Creating it first fixed the error.

  15. Fixed: "AzureCliCredential authentication failed: Azure CLI authentication failed due to an unknown error"

    My .NET agent API answered every request with RUN_ERROR, and its log said AzureCliCredential authentication failed due to an unknown error, followed by AADSTS9002313. The Azure CLI's own sign-in had expired; az login fixed the app without a code change.

  16. Fixed: "AADSTS9002313: Invalid request. Request is malformed or invalid." in Azure CLI

    Every Azure CLI command that needed a token failed with AADSTS9002313. The --debug log showed the real cause, AADSTS50078: my multifactor sign-in had expired under the tenant's policy. az login fixed it.

Tuesday, November 10, 2026

14 of 27 posts

  1. Build an Overtime Timesheet App in Power Apps — Part 9: Show Approvers What's Waiting

    Give approvers a screen in the overtime app that lists every entry waiting for their decision: a Power Apps flow finds who's asking, reads the pending entries they can't open in SharePoint, and returns only their departments' entries as JSON for a gallery.

  2. How to See What a Canvas App Uses with Show Dependencies in Power Apps

    List the environment variables, flows and other solution components a canvas app uses: in its solution, the app's More commands, Advanced, Show dependencies, Uses tab. The list follows the app's published version, so publish before you check.

  3. How to Find Apps Shared with You in Power Apps

    Find the canvas apps other people have shared with you: sign in to Power Apps, select Apps, then Shared with me, and open an app with More commands, Play. Selecting the name opens it for editing, which a User can't do.

  4. How to Share a Canvas App with Specific People in Power Apps

    Share a canvas app with named people in Power Apps: select the app, Share, add each person, keep the User permission, and Share. Check Additional data access first: a flow listed there must be shared with the same people.

  5. How to Refresh a Flow in a Canvas App in Power Apps

    After changing a flow in Power Automate, update the canvas app that runs it: in Power Apps Studio's Power Automate pane, open the flow's More menu, select Refresh, wait for Refreshing to finish, then save and publish the app.

  6. How to Handle a Failed Flow Call in Power Apps

    Show your own message when a flow call fails in a canvas app instead of Power Apps' raw Run failed banner: wrap FlowName.Run() in IfError, keep a failure flag, notify with Notify, and show the failure in a label that stays on the screen.

  7. How to Turn JSON Text into a Table with ParseJSON in Power Apps

    Turn a JSON array returned as text, for example by a flow, into a typed Power Apps table: ParseJSON reads the text, ForAll goes through the array, and Value, Text and DateTimeValue convert each field from a Dynamic value.

  8. How to Run a Flow and Use Its Result in Power Apps

    Run a Power Automate flow from a canvas app with FlowName.Run() in a button's OnSelect, keep what it returns in a context variable, show a loading spinner while it runs, and load it when the screen opens with Select from OnVisible.

  9. How to Add a Flow to a Canvas App in Power Apps

    Add an existing Power Automate flow to a canvas app in Power Apps Studio: open the Power Automate pane from the left bar's More menu, select Add flow, pick the flow from a solution in this environment, and find it under In your app with the name formulas use.

  10. How to Share a Flow with Run-Only Users in Power Automate

    Let people run a flow, from a button or a canvas app, without being able to edit it: on the flow's details page, Run only users, Edit, add people or a group, check Connections Used and Save. Apps that call a solution flow need it.

  11. How to Choose the Connections Run-Only Users Use in Power Automate

    Decide, for each connector in a shared flow, whether it runs with the person's own connection or yours: Run-only users, Edit, Connections Used, Provided by run-only user or Use this connection. The example identifies the caller with theirs and reads SharePoint with the owner's.

  12. How to Return a Table from a Flow to Power Apps as JSON in Power Automate

    Respond to a Power App or flow has no table output, so send a list of records as JSON text: shape it with Select, turn it into text with string(), return it as a Text output, and turn it back into a table in the app with ParseJSON and ForAll.

  13. How to Send Values Back to Power Apps from a Flow in Power Automate

    Return results from a flow to the canvas app that ran it with Respond to a Power App or flow: add an output of type Text, Yes/No, File, Email, Number or Date, name it, set its value, and read it in the app as FlowName.Run().name.

  14. How to Keep Several Fields from Each Item with Select in Power Automate

    Reshape SharePoint items into small objects with only the fields you need using Select in Power Automate: Map in key and value mode, one row per field, with your own key names. The example keeps seven fields of each overtime entry for a canvas app.