Installer fails during "jupyter labextension install jupyterlab_scheduler"

[oj-m]

`jupyterlab_scheduler@latest' is not in the npm registry.

$ jupyter labextension install jupyterlab_scheduler
An error occured.
ValueError: "jupyterlab_scheduler" is not a valid npm package
See the log file for details:  /tmp/jupyterlab-debug-s1rocfg6.log

$ cat /tmp/jupyterlab-debug-s1rocfg6.log
Node v15.11.0

Yarn configuration loaded.
> /usr/bin/npm pack jupyterlab_scheduler
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/jupyterlab_scheduler - Not found
npm ERR! 404 
npm ERR! 404  'jupyterlab_scheduler@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:

[SauravL3010]

(base) C:\Users\Desktop>jupyter labextension install jupyterlab_scheduler
An error occured.
ValueError: "jupyterlab_scheduler" is not a valid npm package
See the log file for details:

[mromanelli9]

I think it is because it was removed from npm (the package manager), or it was never there.
You need to follow the instructions for a development install:

npm install
npm run build:lib
jupyter labextension install .

[jovanni-hernandez]

Hi - Yeah this has to do with me missing a step when I packaged the last version, I failed to upload it to npm, but didn't notice as my dev machine had all the relevant npm components already installed on it. I'm trying to rectify this issue now, but during my hiatus another user @zhou87 published the package. This is now causing conflicts as I've since made some updates to the plugin, but can't update the npm package. I shot Zhao an email to gain control of that npm package so I can update it to mirror the latest version and close this out for good.

[jovanni-hernandez]

Still waiting on @zhao87 to give me ownership of the NPM repository. Until then, the NPM version is dated.

[sam2332]

is this still an issue? should we add a message to the readme? @jovanni-hernandez

[jovanni-hernandez]

@sam2332 thanks for bubbling this back up. Sadly it's still an issue... @zhou87 never surrendered the NPM entry so it looks like I'll have to change the package name slightly. Overall this plugin needs to be bumped up to the latest version of jupyter anyways. Happy to take any PRs, otherwise it'll probably be a few weeks before I get around to this.

[sam2332]

I will be submitting some PR's. One of the big things we need to correct is the cron regex It doesn't allow for two digit interval Offsets
I have also found a bug with the listing of crown jobs that involves the schedule getting manhandled by another regex

[jovanni-hernandez]

Awesome, I really appreciate any contributions. This little plugin has been super helpful in some of my projects, glad to see it be of use to others!