We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm trying to use automapper in a vue project and since the last update I cannot require the transformer plugin. I get this error:
My webpack config looks like this:
Works fine if i downgrade to version 8.3.7
No response
Be able to require the tranformer plugin for my webpack config.
@automapper/core
@automapper/classes
@automapper/nestjs
@automapper/pojos
@automapper/mikro
@automapper/sequelize
8.4.0
The text was updated successfully, but these errors were encountered:
fix: add exports field since web:rollup does not add it by default
a2c2df1
ISSUES CLOSED: #485, #483
Please give this another try with the latest
Sorry, something went wrong.
nartc
No branches or pull requests
Is there an existing issue for this?
Describe the issue
I'm trying to use automapper in a vue project and since the last update I cannot require the transformer plugin.

I get this error:
My webpack config looks like this:

Works fine if i downgrade to version 8.3.7
Models/DTOs/VMs
No response
Mapping configuration
No response
Steps to reproduce
No response
Expected behavior
Be able to require the tranformer plugin for my webpack config.
Screenshots
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.4.0
Additional context
No response
The text was updated successfully, but these errors were encountered: