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
Is your feature request related to a problem? Please describe.
When importing multiple plugins into an Angular project, you have to import as because all plugins export under the same plugin variable name.
Example:
import { plugin as pluginBreadcrumbsNetwork } from "@appsignal/plugin-breadcrumbs-network"
import { plugin as pluginPathDecorator } from "@appsignal/plugin-path-decorator"
Describe the solution you'd like
Give each export of each plugin a unique name. For example:
import { pluginBreadcrumbsNetwork } from "@appsignal/plugin-breadcrumbs-network"
import { pluginPathDecorator } from "@appsignal/plugin-path-decorator"
The text was updated successfully, but these errors were encountered:
timanrebel
changed the title
Exporting plain as plugin is not easy when using multiple plugins
Exporting plugin as plugin is not easy when using multiple plugins
Jan 8, 2021
Is your feature request related to a problem? Please describe.
When importing multiple plugins into an Angular project, you have to
import as
because all plugins export under the same plugin variable name.Example:
Describe the solution you'd like
Give each export of each plugin a unique name. For example:
The text was updated successfully, but these errors were encountered: