You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I have a library that I've compiled and I'm trying to run it in a ReactJS application.
This library uses AutoMapper with the classes strategy, and during startup, there are no compilation issues. However, once on the web console, the following error occurs:
Uncaught TypeError: classes_1.classes is not a function
node_modules bundle.js:49154
factory react refresh:6
Webpack 39
mapper.ts:20
js mapper.ts:20
factory react refresh:6
Webpack 39
The code in my library is similar (if not identical) to the documentation:
import {classes as classesFunction} from "@automapper/classes";
import {CamelCaseNamingConvention, createMapper, Mapper} from "@automapper/core";
export const mapper: Mapper = createMapper({
strategyInitializer: classesFunction(),
namingConventions: {
source: new CamelCaseNamingConvention(),
destination: new CamelCaseNamingConvention(),
},
})
Is there an existing issue for this?
Describe the issue
Hello, I have a library that I've compiled and I'm trying to run it in a ReactJS application.
This library uses AutoMapper with the
classes
strategy, and during startup, there are no compilation issues. However, once on the web console, the following error occurs:The code in my library is similar (if not identical) to the documentation:
The result of the compilation:
Do you have any insights regarding this issue? Thank you in advance!
Models/DTOs/VMs
No response
Mapping configuration
No response
Steps to reproduce
No response
Expected behavior
ReactJS application to work without any log errors
Screenshots
No response
Minimum reproduction code
No response
Package
@automapper/core
@automapper/classes
@automapper/nestjs
@automapper/pojos
@automapper/mikro
@automapper/sequelize
Other package and its version
No response
AutoMapper version
8.7.7
Additional context
NodeJS 18.6
MacOS 13
The text was updated successfully, but these errors were encountered: