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
The last commit of the master branch was more than 3.5 years ago, relevant pull requests remain unmerged, offers to support maintenance remain unanswered and no one has heard from @alinemorelli anymore. We therefore tried to contact via email and LinkedIn, but without success.
All in all, it sounds to us like an abandoned repo, which creates certain problems for current and future users. As soon as someone wants to use CSP and load the GTM script from a custom domain, they can't get any further. Although there are forks for each of the two topics, we couldn't find one that further developed the package as a whole.
- import TagManager from 'react-gtm-module'+ import TagManager from '@sooro-io/react-gtm-module'
Who exactly is “we”?
We are Sooro, a small company from Germany that helps other companies implement, improve and/or verify their tracking, with a focus on server-side tracking. In the course of our work, we have come across the outdated package several times, so we thought it would be good if someone finally took care of the repo/package.
The text was updated successfully, but these errors were encountered:
The last commit of the master branch was more than 3.5 years ago, relevant pull requests remain unmerged, offers to support maintenance remain unanswered and no one has heard from @alinemorelli anymore. We therefore tried to contact via email and LinkedIn, but without success.
All in all, it sounds to us like an abandoned repo, which creates certain problems for current and future users. As soon as someone wants to use CSP and load the GTM script from a custom domain, they can't get any further. Although there are forks for each of the two topics, we couldn't find one that further developed the package as a whole.
We would like to take care of the matter and have therefore created a new repo and published an NPM package.
What has changed?
nonce
arg)source
arg)events
arg (breaking change!)Some of the topics already had pull requests, others didn't. We have a few more ideas for improvements, which we want to tackle later.
How to migrate?
We added a migration guide to the readme but it's for the majority of the users quite simple.
It's just about switching the packages via NPM.
And adjusting the imports in your code:
Who exactly is “we”?
We are Sooro, a small company from Germany that helps other companies implement, improve and/or verify their tracking, with a focus on server-side tracking. In the course of our work, we have come across the outdated package several times, so we thought it would be good if someone finally took care of the repo/package.
The text was updated successfully, but these errors were encountered: