Support Forum

Hi, abbeyng!

Thank you for the additional information.
I was able to reproduce this error.
This is the issue for the fix
https://github.com/bryntum/support/issues/8815

Please subscribe to it get updates.

Hi, Shashank! This config https://bryntum.com/products/grid/docs/api/Grid/util/TableExporter#config-indentationSymbol defaults to '\u00A0\u00A0\u00A0\u00A0' . This outputs spaces in cvs as non-breaking spaces This works for xlsx export, but breaks csv. Try using this config in app features : { excel...

Hi! Please confirm which exact commands you have run, which files were created for accessing Bryntum registry? These commands, executed on clean system in empty project folder are enough to install package. npm config set "@bryntum:registry=https://npm.bryntum.com" npm login --auth-type=le...

Hi! If you have created .npmrc files for trial login, please remove all and recreate with valid licensed login. Logout from repository and login again. npm logout --registry=https://npm.bryntum.com npm login --auth-type=legacy --registry=https://npm.bryntum.com Please check package name for licensed...

Hi!

Great to hear that! Thanks for the information!

Hi! Please try all of the below instructions and reply what you have received on each step. 1) Login to Customer Zone (https://customerzone.bryntum.com/login) with email which you want to use for npm. Open "Licenses" section on the left and check your licenses there. Calendar and Scheduler...

Hi!

Please try to login with product.engineering@k.... email.

Hi!

Could you please use npm login with the email, which has both active licenses in Customer Zone?

Please reach me in PM with email which was used for npm login if you still have installation problems.

Hi!

calendar-react is free package, which doesn't require license, so it can be installed under login with Scheduler license.

Please make sure you have one login which have both licenses in Customer Zone.
Please contact Bryntum licensing department for the details.

Hi!

Please try removing global npm packages and try again.
Seems that you use minipass-fetch npm module, which is nonstandard one.