RepositoryNotFoundError w/ serverless offline

Issue type: [x] bug report

Database system/driver: [x] postgres

TypeORM version: [x] 0.2.7 (or put your version here)

Steps to reproduce or a small repository showing the problem:

1. Use ormconfig.json, set entities to something like "**/entities/*.{js,.ts}"
2. Run serverless offline start
3. Try to get repo like: this.repo = connection.getRepository<User>(User)
4. I also tried like this.repo = connection.getRepository<User>('User')

Result: RepositoryNotFoundError: No repository for “User” was found. Looks like this entity is not registered in current “dev” connection?

I know my entities are set correctly in my ormconfig.json file b/c my database tables are all synced correctly, but I can’t get a repo to do any work.

Please help!

Here’s my ormconfig.json:

{
    "name": "dev",
    "type": "postgres",
    "host": "localhost",
    "port": 5432,
    "username": "postgres",
    "database": "postgres",
    "entities": [
        "**/entities/*.{js,.ts}"
    ],
    "synchronize": true,
    "logging": false
}

Here’s what my Database class looks like:

export class Database {
    private connectionManager: ConnectionManager

    constructor() {
        Logger.info(`Database()`)
        this.connectionManager = getConnectionManager()
    }

    public async getConnection(): Promise<Connection> {
        Logger.info(`Database.getConnection()`)

        let connection: Connection

        try {
            connection = this.connectionManager.get(process.env.CONNECTION_NAME)
        }
        catch (e) {
            Logger.warn(`Database.getConnection()-error=${e}`)

            // read connection options from ormconfig file (or ENV variables)
            const connectionOptions = await getConnectionOptions(process.env.CONNECTION_NAME);
            Object.assign(connectionOptions, { namingStrategy: new SnakeNamingStrategy() });

            Logger.info(`Database.getConnection()-connectionOptions=${inspect(connectionOptions)}`)

            connection = await createConnection(connectionOptions)
        }

        return connection
    }
}

[kvarela]

@ganesh9596 I actually had to switch back to explicitly calling out the entities because I switched I had to minify my code (using Browserify) and after minification it no longer makes sense to have a directory structure.

But here’s my current connectionOptions for reference:

export const connectionOptions: ConnectionOptions = {
    name: `default`,
    type: `postgres`,
    synchronize: true, // todo: remove for production, should be replaced with formal migrations once we're launched
    logging: false,
    replication: {
        master: {
            host: process.env.DB_HOST,
            username: process.env.DB_USERNAME,
            database: process.env.DB_NAME,
            password: process.env.DB_PASSWORD,
            port: 5432
        },
        slaves: [
            {
                host: process.env.DB_HOST_SLAVE,
                username: process.env.DB_USERNAME,
                database: process.env.DB_NAME,
                password: process.env.DB_PASSWORD,
                port: 5432
            }
        ]
    },
    namingStrategy: new SnakeNamingStrategy(),
    // This causes problems with minification since there's no longer a directory structure
    // entities: [__dirname + '/entities/*.*']
    entities: [
        Amenity,
        City,
        Hotel,
        HotelAmenity,
        HotelBooking,
        HotelPhoto,
        HotelPolicy,
        HotelRoom,
        HotelSupplyUpdate,
        HotelTag,
        Neighborhood,
        Policy,
        Tag,
        User
    ]
}

[joaovpmamede]

@warnerpinz https://www.npmjs.com/package/typeorm-naming-strategies