A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/maxGraph/maxGraph/discussions/41 below:

Steps required for publishing package · maxGraph/maxGraph · Discussion #41 · GitHub

Skip to content Navigation Menu Search code, repositories, users, issues, pull requests...

Saved searches Use saved searches to filter your results more quickly

Sign up 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 Steps required for publishing package #41

May 12, 2021 · 3 comments · 4 replies

{{actor}} deleted this content .

-

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:

  1. fix on a name, as discussed in Rename the project, licensing issue with name "mxGraph" #23
  2. rename jsGraph/mxgraph github repository to jsGraph/new-name - Done: maxGraph/maxGraph
  3. decide on what the version should be. It has been proposed that version 5.0 is good
  4. create a branch from which we can publish to npmjs.com
  5. from @lreading 's comment below, wind back this branch to a clean licence version
  6. publish max-graph/maxGraph on npmjs.com
  7. nice to have a note on the existing jGraph/mxgraph package that it has been superseded - would need permissions

The Threat Dragon and other projects can start using the new package

Beta Was this translation helpful? Give feedback.

You must be logged in to vote

{{actor}} deleted this content .

-

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.

You must be logged in to vote

1 reply

-

Hi, the package will be made from the development branch.
There are some pending works in a dedicated branch that contains the migration to Typescript, tree shaking capacities and more. See #51 for more details.

Beta Was this translation helpful? Give feedback.

{{actor}} deleted this content .

-

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.

You must be logged in to vote

1 reply

-

@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.

You must be logged in to vote

2 replies

-

See #41 (comment)
Next time, please avoid duplicating comments, put a reply on existing comments instead. This will avoid the spammy effect.

Beta Was this translation helpful? Give feedback.

Heading

Bold

Italic

Quote

Code

Link

Numbered list

Unordered list

Task list

Attach files

Mention

Reference

Menu reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji

You can’t perform that action at this time.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4