Skip to main content

Backstage failing to start with Schema Error

I have been testing Backstage and all was going well till I did a yarn install this afternoon and now the whole thing has died on me :)

Whenever I try to run yarn dev it errors out with

[0] Loaded config from app-config.yaml
[0] <i> [webpack-dev-server] Project is running at:
[0] <i> [webpack-dev-server] Loopback: http://localhost:3000/, http://[::1]:3000/
[0] <i> [webpack-dev-server] Content not from webpack is served from '/Users/robertsa1/src/scratch/dev10/bleh/backstage/packages/app/public' directory
[0] <i> [webpack-dev-server] 404s will fallback to '/index.html'
[0] <i> [webpack-dev-middleware] wait until bundle finished: /catalog?filters%5Bkind%5D=component&filters%5Buser%5D=all
[1] Backend failed to start up Error: Invalid configuration schema in ../../node_modules/@backstage/plugin-proxy-backend/config.d.ts, the following definitions are not supported:
[1]
[1]   Partial<{[key:string]:string;Authorization:string;authorization:string;'X-Api-Key':string;'x-api-key':string;}>
[1]     at /Users/robertsa1/src/scratch/dev10/bleh/backstage/node_modules/@backstage/config-loader/dist/index.cjs.js:348:15
[1]     at Array.map (<anonymous>)
[1]     at compileTsSchemas (/Users/robertsa1/src/scratch/dev10/bleh/backstage/node_modules/@backstage/config-loader/dist/index.cjs.js:322:27)
[1]     at async collectConfigSchemas (/Users/robertsa1/src/scratch/dev10/bleh/backstage/node_modules/@backstage/config-loader/dist/index.cjs.js:299:21)
[1]     at async Object.loadConfigSchema (/Users/robertsa1/src/scratch/dev10/bleh/backstage/node_modules/@backstage/config-loader/dist/index.cjs.js:481:15)
[1]     at async Object.createConfigSecretEnumerator (/Users/robertsa1/src/scratch/dev10/bleh/backstage/node_modules/@backstage/backend-app-api/dist/index.cjs.js:195:18)
[1]     at async loadBackendConfig (/Users/robertsa1/src/scratch/dev10/bleh/backstage/node_modules/@backstage/backend-common/dist/index.cjs.js:400:28)
[1]     at async main (webpack-internal:///./src/index.ts:83:20)

I cannot see how this is now an issue when this file has been present since I started my work.

even going and doing npx @backstage/create-app@latest in a new folder comes up with the same error....

Any advice much appreciated.

Via Active questions tagged javascript - Stack Overflow https://ift.tt/vefli7C

Comments

Popular posts from this blog

Prop `className` did not match in next js app

I have written a sample code ( Github Link here ). this is a simple next js app, but giving me error when I refresh the page. This seems to be the common problem and I tried the fix provided in the internet but does not seem to fix my issue. The error is Warning: Prop className did not match. Server: "MuiBox-root MuiBox-root-1" Client: "MuiBox-root MuiBox-root-2". Did changes for _document.js, modified _app.js as mentioned in official website and solutions in stackoverflow. but nothing seems to work. Could someone take a look and help me whats wrong with the code? Via Active questions tagged javascript - Stack Overflow https://ift.tt/2FdjaAW

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console