5 posts tagged with "package-manager"

Howdy! This release was brought to you by an unforseen change on the Nexus side, which caused external UI tabs to be saved with the settings. That in itself wouldn't be too bad if it didn't mean that critical information that made the tab an UI element was lost. So on restoring these UI elements, the whole UI would crash and all you were left with is a blank screen.

This release contains a workaround for the issue. Since the UI is already broken for most of you, the workaround I used to keep my packages was to log in via a mobile app (Android in my case, iOS should work as well, but not the browser!), gointo the settings, then Custom Tabs and remove the npkg_ui tab. If you then log into the webbrowser, the package manager should work on the browser and allow you to update the package manager with the workaround.

Additional Changes

Since I was working with the webpack entrypoint anyways, I extended the Nexus typings by a few interfaces and functions to remove eslint and TypeScript magical comments.

If you like the project, please consider leaving a star on the GitHub project and sponsoring me.

This is the first release of the scripts within the new monorepo structure. For some background about the changes see here. Were're here now to celebrate the release itself! ❤️

New Script: Queue Manager

The queue manager introduced with this release is meant to make it easier to use the in-game queueing with your scripts. It tracks the queue, allows you to queue client-side commands and tries to integrate as seamlessly as possible with external queue sources.

This release does not allow for the foll flexibility of the in-game queueing yet (like prepending or adding at certain places in the queue), but it should be enough to vet the implementation. For more details, please refer to the documentation.

Developer Documentation

Due to the switch to the monorepo structure, I added a lot of additional developer documentation, like READMEs, a Code of Conduct and Contribution Guidelines. Please have a look!

More Infrastructure Changes

In addition to the overall layout change of the repository and all linked changes, I also switch from dependabot to renovate. This hopefully further decreases the dependency maintenance burden as dependency upgrades are now bundled together. Currently, this still has some kinks to straighten out, but I'm sure we will get there.

Other Changes

Most packages should now export their classes as a global library, which webpack then can use to avoid bundling all the code with yours. This is still untested, so expect further changes in that area.

Additionally, quite a few of the linter and test rules saw some harmonization, which prompted a few non-code changes to follow best practices.

If you like the project, please consider leaving a star on the GitHub project and sponsoring me.

This bugfix release fixes the issue that makes all actions for reflexes (eg calling scripts, coloring lines etc) disappear when installing a package through the package manager.

Additionally, version 0.2.2 fixes an issue in the website infrastructure.

I hope nobody lost important changes through this!

If you like the project, please consider leaving a star on the GitHub project and sponsoring me.

I'm happy to announce that the project reached a huge milestone. It now handles dependencies of packages that are listed in package repository.

Handling dependencies

Whenever the package manager installs a package, it checks, whether it has other packages that are required for it to function correctly. These packages are first searched in the local package list. If they are installed, the package manager proceeds to install the original package as normal. If a dependency is not installed, the package manager will first install the dependency, before proceeding with the actual requested package installation.

The package manager will also make sure, that dependencies are listed in the correct order. This makes sure that the initialization of a package is only attempted when all dependencies are already initialized. No more documenting "and make sure package A is above package B". This happens both after the installation and update of a package.

UI improvements

The UI also got some improvements. You can now show package details within the window, including version, description, dependencies and a link to the website.

The UI main page got some layout imprvements by using icons instead of text for buttons, which makes the page much cleaner.

Closing words

If these features got you interested, please feel free to either open an issue about including your package in the package listing or contact me on the Achaea or Nexus discrod if you need more information. You can also send me a direct message.

If you like the project, please consider leaving a star on the GitHub project and sponsoring me.

This is the very first release of the Nexus Package Manager. This MVP (Minimal Viable Product), which contains only a bare minimum of features. These include a basic UI, the retrieval of package data from a remote location as well as installation, update and removal of packages. All of this functionality is also provided by the Nexus UI, with the exception of a package listing. So right now it can be used as a way to discover new packages.

Future plans include the tracking and installation of dependencies, version handling and notification of new updates for installed packages.

The success of this project is strongly linked with how extensive the list of available packages is. So, if you know of a package or have authored one yourself, please head over to https://github.com/keneanung/nexus-package-repository and either add the package via pull request or open an issue so I can add it.

v0.1.1 Infrastructure fix

This version bump was only for infrastructure fixes. The package was not modified.

If you like the project, please consider leaving a star on the GitHub project and sponsoring me.