How do I know my backend extension was loaded

[daleasberry-n]

I see my module.ts in /browser-app/src-gen/backend/server.js. I've fixed all the errors, but, I don't see any of the code in the extensions being executed. Am I missing something?

[msujew]

Hey @daleasberry-n,

can you give a bit more info? Like some of your code or maybe even a reproducible example?

Generally, the backend will print out the names of all loaded BackendApplicationContribution entries during the startup phase.

[daleasberry-n]

resolver.ts:
@Injectable()
export class Resolver implements BackendApplicationContribution

server.js:
await load(require('tooling/lib/backend/configure/resolver-module'));

resolver-module.ts:
import { ContainerModule } from 'inversify';
import { Resolver } from './config-resolver';
import * as path from 'path';

export default new ContainerModule(bind => {
const defaultConfigPath = path.join(__dirname, 'config.json');
bind('ConfigPath').toConstantValue(defaultConfigPath);
bind(Resolver).toSelf().inSingletonScope();
});

entire log output:
2025-01-16T21:46:08.319Z root INFO Backend DefaultMessagingService.initialize: 11.7 ms [Finished 0.209 s after backend start]
2025-01-16T21:46:08.319Z root INFO Backend Object.initialize: 10.8 ms [Finished 0.209 s after backend start]
2025-01-16T21:46:08.319Z root INFO Backend LocalizationServerImpl.initialize: 10.7 ms [Finished 0.209 s after backend start]
2025-01-16T21:46:08.321Z root INFO configured all backend app contributions
2025-01-16T21:46:08.321Z root INFO Backend WebsocketEndpoint.onStart: 0.8 ms [Finished 0.213 s after backend start]
2025-01-16T21:46:08.322Z root INFO Configuration directory URI: 'file:///Users/daleasberry/.theia'
2025-01-16T21:46:08.325Z root INFO Theia app listening on http://127.0.0.1:3000.
2025-01-16T21:46:08.326Z root INFO Backend DefaultWorkspaceServer.onStart: 4.8 ms [Finished 0.217 s after backend start]
2025-01-16T21:46:08.326Z root INFO Finished starting backend application: 0.0 ms [Finished 0.217 s after backend start]
2025-01-16T21:46:18.455Z root INFO Reconnecting failed for 7aeca59c-2a98-4ee1-b33f-db70fe6a1d63
2025-01-16T21:46:18.467Z root INFO creating connection for 7aeca59c-2a98-4ee1-b33f-db70fe6a1d63
2025-01-16T21:46:18.491Z root INFO reconnect failed on 3ZnECvJNIVybZqOLAAAB
2025-01-16T21:46:18.491Z root INFO sending initial connect on undefined
2025-01-16T21:46:18.491Z root INFO reconnect failed on undefined
2025-01-16T21:46:18.491Z root INFO sending initial connect on undefined
2025-01-16T21:46:18.491Z root INFO sending reconnect on -uhQXfq9l8wpuNIxAAAE
2025-01-16T21:46:18.491Z root INFO initial connect received on -uhQXfq9l8wpuNIxAAAE
2025-01-16T21:46:18.491Z root INFO initial connect received on -uhQXfq9l8wpuNIxAAAE

if I put a console.log('got here') as the first line in the new ContainerModule, it'll print it to the log. But, if I put it after any bind(...), it won't.

[msujew]

You need to actually bind the Resolver class as a BackendApplicationContribution in your container module. Otherwise inversify has no idea that it's supposed to be one (interface definitions are deleted when compiling TypeScript to JavaScript):

bind(BackendApplicationContribution).toService(Resolver);

[daleasberry-n]

One step closer. Of course issues... ;-)

Thanks!