Our blazing fast Grid component built with pure JavaScript


Post by rafael.tietz »

Hello, I am having the same issue again.

npm ERR! code E401
npm ERR! Unable to authenticate, your authentication token seems to be invalid.
npm ERR! To correct this please trying logging in again with:
npm ERR!     npm login

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

There was a recent change in my licensing, which probably is causing the issue.
I am trying to install Bryntum Grid, and Bryntum Scheduler Pro.

Already tried logout/login again, it did not work. Can someone help with this?


Post by sergey.maltsev »


Post by rafael.tietz »

Everything is correct in the app. I have been working with the libraries for the past year or so.
I am just trying to recreate the packages-lock.json but I get this error.
Already checked the login, and it is working perfectly. I can see my license on the Costumer Zone, but they changed recently because the company needed to add other developers.

There are also some other expired ones. Which can be causing the error, the same happened before (check the start of the thread).

Anyway, here is the full error log:

7684 verbose stack HttpErrorAuthUnknown: Unable to authenticate, need: Basic, Bearer
7684 verbose stack     at C:\Users\..\AppData\Roaming\npm\node_modules\npm\node_modules\npm-registry-fetch\lib\check-response.js:78:17
7684 verbose stack     at runMicrotasks (<anonymous>)
7684 verbose stack     at processTicksAndRejections (node:internal/process/task_queues:96:5)
7685 verbose statusCode 401
7686 verbose pkgid @bryntum/schedulerpro@https://npm.bryntum.com/@bryntum%2fschedulerpro/-/schedulerpro-5.2.7.tgz
7687 verbose cwd C:\Users\..\Documents\Projects\I2-New\git\i2r-repo\i2r-app
7688 verbose Windows_NT 10.0.19044
7689 verbose node v16.15.1
7690 verbose npm  v8.8.0
7691 error code E401
7692 error Unable to authenticate, your authentication token seems to be invalid.
7693 error To correct this please trying logging in again with:
7693 error     npm login
7694 verbose exit 1
7695 timing npm Completed in 182157ms
7696 verbose unfinished npm timer reify 1674076792250
7697 verbose unfinished npm timer reify:unpack 1674076832448
7698 verbose unfinished npm timer reifyNode:node_modules/@bryntum/schedulerpro 1674076832820
7699 verbose unfinished npm timer reifyNode:node_modules/@bryntum/grid 1674076832821
7700 verbose code 1

Thank you.


Post by sergey.maltsev »

Hi!

Please check if you use .npmrc file in project folder and it has valid token.


Post by rafael.tietz »

I have removed the .npmrc file and tried to install the packages again. Did not make any difference.
This is happening in my localhost environment, where I have logged to the npm repository already.


Post by sergey.maltsev »

Could you please try installing packages in any empty folder using this guide?
https://bryntum.com/products/schedulerpro/docs/guide/SchedulerPro/npm-repository#installing-licensed-packages

If this didn't work please reach me at PM here with login name you used for authorizing so I can check access rights.


Post by sergey.maltsev »

Hi, Rafael!

We've have fixed issue with installing packages.
Please relogin and install packages again.
Also please confirm if this works for you.


Post by rafael.tietz »

Hey. Yes, it is working again.
Do you mind explaining what was done to fix this?
I would like to document this on my side so that if it happens again, we can make more assertive requests to you guys.
Thank you.


Post by sergey.maltsev »

Hi!

It was our internal authentication procedure issue.
No actions required from your side.
Thank you for reaching us with this issue.


Post Reply