Rafał Dzięgielewski
Rafał Dzięgielewski
@sbassin most if not all of our commercial projects use `@adminjs/typeorm` and we've had no issues with typeorm/styled-components after migrating them to the latest versions. It's difficult to help without...
@sbassin do you have `type: "module"` set in your `package.json`?
AdminJS requires an actual model for junction table to run queries and this kind of model isn't generated automatically by TypeORM. The same applies to other ORMs.
You can make any field editable using resource options configuration
Session store and middleware are created specifically inside AdminJS router so you cannot access the session object in outside routes, you'd have to do something like: ``` export const getAdminRouter...
No, only if you use session middleware with identical options in your other routes.
@njetsy @par5ul1 @wmurphyrd @pacholoamit @absqueued Hi, I've just released this on new `@dev` channel: https://github.com/SoftwareBrothers/better-docs/releases/tag/v2.7.4-dev.1 There's no changelog available because `semantic-release` relies on `feat:` and `fix:` prefixed commits to build...
We're using it internally to generate documentation (https://docs.adminjs.co) for AdminJS: https://github.com/SoftwareBrothers/adminjs-dev
I think it's just a windows issue where it doesn't allow you to move files from one partition to another
The latest versions of AdminJS packages can only be used in ESM projects. If your project is CommonJS, you'd have to downgrade to AdminJS v6 and use it's compatible dependencies.