Captain Fizzbin

Also ran into this bug, but we're unable to downgrade to 1.9.1. Can confirm it's related to building the container while a Cache is available. Disabling the cache allows the...

Here's what I did to get knex to reuse the Backstage config: ```ts // plugins/your-plugin-backend/knexfile.ts import { Knex } from 'knex'; import { getVoidLogger, loadBackendConfig } from '@backstage/backend-common'; import {...

knexfile.ts for Backstage 1.29: ```ts import { Knex } from 'knex'; import { ConfigSources } from '@backstage/config-loader'; import { resolvePackagePath } from '@backstage/backend-plugin-api'; const PLUGIN_ID = 'my-plugin'; module.exports = async...

knexfile.ts for backstage 1.31: ```ts import { Knex } from 'knex' import { ConfigSources } from '@backstage/config-loader' import { resolvePackagePath } from '@backstage/backend-plugin-api' import pluginPkgJson from './package.json' const PLUGIN_ID =...

Can you provide more information about what the dependency issue is?

Looks like TC39 has decided that decorators on exports can be either before `export` or after `expert` (but not both) https://github.com/tc39/proposal-decorators/issues/69#issuecomment-1414289895

Can confirm that this is still an issue for Backstage 1.29 with a fresh install of both Backstage and the toolbox plugin: https://github.com/CptnFizzbin/backstage-toolbox-test/commit/03d20c78d1705f9aa589479152f91bf3cb638a4d

I can confirm that 1.22.1 builds fine with 1.30.0-next.3

Same error message also appears when trying to send a `https` request to a `http` endpoint

For those that come across this issue, a work around I found is that you can remove the __archiveUrl portion from the string in package.json: From ```json { "resolutions": {...