Our pure JavaScript Scheduler component


Post by aaneeshg »

Hi Team,

We have successfully completed our scheduler POC project with bryntum, but still we are using local dependency from downloaded trial folder(scheduler-3.1.5-trial).We are going to start development ,So we cannot carry local (scheduler-3.1.5-trial) folder in all environment.Could you please give me good solution for to remove local bryntum dependency or please share bryntum dependency available in npm registry.How does these dependencies work when we buy license?

Have to remove below dependency(Please check screen shot)

bryntum-resources : Able to remove

bryntum-scheduler

bryntum-vue-shared

I tried to install "bryntum-scheduler" and "bryntum-vue-shared" (using npm install comment) but getting below error.

verbose Windows_NT 10.0.14393
verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\..\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "bryntum-vue-shared"
verbose node v10.16.0
verbose npm v6.14.5
error code E404
error 404 Not Found - GET https://registry.npmjs.org/bryntum-vue-shared - Not found
error 404
error 404 'bryntum-vue-shared@latest' is not in the npm registry.
error 404 You should bug the author to publish it (or use the name yourself!)
error 404 Note that you can also install from a
error 404 tarball, folder, http url, or git url.
verbose exit [ 1, true ]

Thanks in
Advance

Attachments
dependency
dependency
dependency.JPG (60.46 KiB) Viewed 506 times

Post by Maxim Gorkovsky »

Hello.
There are plans to make our sources available through NPM, but work is still in progress. This feature certainly will be announced, stay tuned. Until then you'll have to use file or set up company-local npm registry.

How does these dependencies work when we buy license?

They work identically, but you will have full access to source code without trial limitations.


Post Reply