Our pure JavaScript Scheduler component


Post by Alipalengara »

Hi,

We are trying to integrate the Bryntum Scheduler Pro 4.0.1 trial into Angular Project and we are facing the below error when we accessing the Bryntum NPM Repository as given in document.

We are getting the error on below command.
npm i @bryntum/schedulerpro-angular@4.1.0

Error details .

F:\Projects\Proj\Development\Source\WorkingCopy\UI>npm i @bryntum/scheduler-angular@4.1.0
npm ERR! code E403
npm ERR! 403 403 Forbidden - GET https://npm.bryntum.com/@bryntum%2fscheduler - user ali.palengara..gdi.ae is not allowed to access package @bryntum/scheduler
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy.
npm ERR! 403
npm ERR! 403 It was specified as a dependency of '@bryntum/scheduler-angular'
npm ERR! 403

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

Thanks
Ali PP


Post by sergey.maltsev »

Hi!

Please use these commands in order to install trial:

npm i @bryntum/scheduler@npm:@bryntum/scheduler-trial@4.1.0
npm i @bryntum/scheduler-angular@4.1.0

or add manually to package.json:

"dependencies": {
"@bryntum/scheduler": "npm:@bryntum/scheduler-trial@4.1.0",
"@bryntum/scheduler-angular": "4.1.0"
}

Trial package info can be found here https://www.bryntum.com/docs/scheduler/#guides/npm-repository.md#trials


Post by Alipalengara »

Hi Sergey,
Many thanks for your response.
We tried to run the above command also. Still we are getting the error as given below. Attached terminal screenshot for reference

Command 1
$ npm i @bryntum/scheduler-angular@4.1.0
Error
npm ERR! code E403
npm ERR! 403 403 Forbidden - GET https://npm.bryntum.com/@bryntum%2fscheduler - user ali.palengara..gdi.ae is not allowed to access package @bryntum/scheduler
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy.
npm ERR! 403
npm ERR! 403 It was specified as a dependency of '@bryntum/scheduler-angular'
npm ERR! 403

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\alipa\AppData\Roaming\npm-cache\_logs\2021-04-12T12_10_38_559Z-debug.log

Command 2
npm i @bryntum/scheduler@npm:@bryntum/scheduler-trial@4.1.0

Error
npm ERR! code E500
npm ERR! 500 Internal Server Error - GET https://npm.bryntum.com/@bryntum%2fscheduler-trial/-/scheduler-trial-4.1.0.tgz

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\alipa\AppData\Roaming\npm-cache\_logs\2021-04-12T12_11_54_627Z-debug.log

Thanks
Ali PP

Attachments
Bryntum-error-msg.PNG
Bryntum-error-msg.PNG (173.14 KiB) Viewed 1880 times

Post by sergey.maltsev »

Hi!

Please change the order of commands as was shown above.
First has to be installing trial package alias.

npm i @bryntum/scheduler@npm:@bryntum/scheduler-trial@4.1.0
npm i @bryntum/scheduler-angular@4.1.0

Also you may need to Cleanup a project. Instructions here.
https://www.bryntum.com/docs/scheduler/#guides/npm-repository.md#troubleshooting


Post by Ivan Somov »

I have the same problem with trial scheduler
After npm install or yarn add I got 500 server error
The order in package.json is right
I also tried separately in console starting from trial package installation

looks like issue on the package storage side.

Attachments
Screenshot at Apr 12 23-15-05.png
Screenshot at Apr 12 23-15-05.png (72.18 KiB) Viewed 1865 times
Screenshot at Apr 12 23-14-10.png
Screenshot at Apr 12 23-14-10.png (21.27 KiB) Viewed 1865 times

Post by sergey.maltsev »

Hi, Ivan.

Please check this troubleshooting section first and make sure you've logged to server.
https://www.bryntum.com/docs/scheduler/#guides/npm-repository.md#troubleshooting

I've just tried the installation like I suggested above.
This is the result.

Install trial package.

E:\Bryntum\source-npm\test>npm i @bryntum/scheduler@npm:@bryntum/scheduler-trial@4.1.0

> @bryntum/scheduler-trial@4.1.0 postinstall E:\Bryntum\source-npm\test\node_modules\@bryntum\scheduler
> node ../scheduler-trial-lib/build.js

npm notice created a lockfile as package-lock.json. You should commit this file.

+ @bryntum/scheduler-trial@4.1.0 (as @bryntum/scheduler)
added 2 packages from 1 contributor in 2.078s

Install angular wrapper package.

E:\Bryntum\source-npm\test>npm i @bryntum/scheduler-angular@4.1.0

+ @bryntum/scheduler-angular@4.1.0
added 2 packages from 2 contributors in 1.668s

Also I had no problems with installing our demos you can find in examples/frameworks folder if you get trial distribution zip.

If you still have a problems please attach a complete error log from the filename which is in console.

Attachments
scheduler-trial.png
scheduler-trial.png (61.87 KiB) Viewed 1857 times

Post by Ivan Somov »

Still have problem. but new description for now

Below log text

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'i',
1 verbose cli   '@bryntum/scheduler@npm:@bryntum/scheduler-trial@4.1.0'
1 verbose cli ]
2 info using npm@6.14.8
3 info using node@v14.15.0
4 verbose npm-session cdb0302dc4b6967f
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 304 https://npm.bryntum.com/@bryntum%2fscheduler-trial 225ms (from cache)
8 http fetch GET 401 https://npm.bryntum.com/@bryntum%2fscheduler-trial/-/scheduler-trial-4.1.0.tgz 208ms
9 silly fetchPackageMetaData error for @bryntum/scheduler@npm:@bryntum/scheduler-trial@4.1.0 Unable to authenticate, need: Basic, Bearer
10 timing stage:rollbackFailedOptional Completed in 1ms
11 timing stage:runTopLevelLifecycles Completed in 2328ms
12 verbose stack Error: Unable to authenticate, need: Basic, Bearer
12 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:107:17
12 verbose stack     at processTicksAndRejections (internal/process/task_queues.js:93:5)
13 verbose statusCode 401
14 verbose pkgid @bryntum/scheduler-trial@4.1.0
15 verbose cwd /Users/ivan.somov/projects/bryntum-try
16 verbose Darwin 19.6.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "i" "@bryntum/scheduler@npm:@bryntum/scheduler-trial@4.1.0"
18 verbose node v14.15.0
19 verbose npm  v6.14.8
20 error code E401
21 error Unable to authenticate, your authentication token seems to be invalid.
22 error To correct this please trying logging in again with:
22 error     npm login
23 verbose exit [ 1, true ]
Attachments
Screenshot at Apr 13 11-32-57.png
Screenshot at Apr 13 11-32-57.png (181.45 KiB) Viewed 1847 times

Post by Ivan Somov »

tried clean cache and use one more other mail
got same issue. log below

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'i',
1 verbose cli   '@bryntum/scheduler@npm:@bryntum/scheduler-trial@4.1.0'
1 verbose cli ]
2 info using npm@6.14.8
3 info using node@v14.15.0
4 verbose npm-session 23fe21fe29fef16a
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 200 https://npm.bryntum.com/@bryntum%2fscheduler-trial 274ms
8 http fetch GET 401 https://npm.bryntum.com/@bryntum%2fscheduler-trial/-/scheduler-trial-4.1.0.tgz 218ms
9 silly fetchPackageMetaData error for @bryntum/scheduler@npm:@bryntum/scheduler-trial@4.1.0 Unable to authenticate, need: Basic, Bearer
10 timing stage:rollbackFailedOptional Completed in 0ms
11 timing stage:runTopLevelLifecycles Completed in 556ms
12 verbose stack Error: Unable to authenticate, need: Basic, Bearer
12 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:107:17
12 verbose stack     at processTicksAndRejections (internal/process/task_queues.js:93:5)
13 verbose statusCode 401
14 verbose pkgid @bryntum/scheduler-trial@4.1.0
15 verbose cwd /Users/ivan.somov/projects/smart-dashboard
16 verbose Darwin 19.6.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "i" "@bryntum/scheduler@npm:@bryntum/scheduler-trial@4.1.0"
18 verbose node v14.15.0
19 verbose npm  v6.14.8
20 error code E401
21 error Unable to authenticate, your authentication token seems to be invalid.
22 error To correct this please trying logging in again with:
22 error     npm login
23 verbose exit [ 1, true ]

Post by sergey.maltsev »

Hi!

We have fixed trial access at our npm server.

Please try to install trial product now with:

npm install @bryntum/scheduler@npm:@bryntum/scheduler-trial@4.1.0

Waiting for your reply.


Post by Ivan Somov »

it works now. thank you!

could you please also help where can I get info how to import default styles for react scheduler?


Post Reply