-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
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
Remove DSM Integration package #238
Labels
Comments
andy-polhill
added a commit
to andy-polhill/canopy
that referenced
this issue
Mar 12, 2021
We have decided to remove Invision DSM and opt for a more manual process of linking examples. The DSM package had a very large dependency tree which was prone to vulnerabilities, these were rarely fixed within an appropriate timeframe. It also forced us into specific versions of dependences and at times held us back from upgrading Storybook. fix Legal-and-General#238
andy-polhill
added a commit
to andy-polhill/canopy
that referenced
this issue
Mar 12, 2021
We have decided to remove Invision DSM and opt for a more manual process of linking examples. The DSM package had a very large dependency tree which was prone to vulnerabilities, these were rarely fixed within an appropriate timeframe. It also forced us into specific versions of dependences and at times held us back from upgrading Storybook. fix Legal-and-General#238
7 tasks
andy-polhill
added a commit
that referenced
this issue
Mar 15, 2021
We have decided to remove Invision DSM and opt for a more manual process of linking examples. The DSM package had a very large dependency tree which was prone to vulnerabilities, these were rarely fixed within an appropriate timeframe. It also forced us into specific versions of dependences and at times held us back from upgrading Storybook. fix #238
🎉 This issue has been resolved in version 5.6.3 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The DSM integration package is causing a few headaches:
It's been agreed between the package should be removed and an alternative method of displaying Angular components in the DSM should be adopted.
The text was updated successfully, but these errors were encountered: