Steps required for publishing package #41
Replies: 3 comments 4 replies
-
|
Will this package be made from the development branch or main branch? I think another step before publishing the package would be reverting a few commits to ensure that the licensing issues are addressed. I can open an issue for that if we need. It's also worth noting that a deprecated notice has been placed on the mxgraph package. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, the package will be made from the development branch. |
Beta Was this translation helpful? Give feedback.
-
|
hi buddy, how are things going with the package release? We sincerely hope that this project can move on, so what can I do for these steps ？ |
Beta Was this translation helpful? Give feedback.
-
|
@lalicw please check #51. You can build the project, play with the examples. |
Beta Was this translation helpful? Give feedback.
-
|
hi buddy, how are things going with the package release? We sincerely hope that this project can move on, so what can I do for these steps ？ |
Beta Was this translation helpful? Give feedback.
-
|
See #41 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
OK，I'll pay attention |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It would be good to release a new jsGraph/mxgraph package on npmjs.com so that Threat Dragon and other projects can start to migrate away from using jGraph/mxgraph.
As I see it the steps required to do this are:
The Threat Dragon and other projects can start using the new package
Beta Was this translation helpful? Give feedback.
All reactions