Our pure JavaScript Scheduler component


Post by andreas-sakellariou »

Hello, I am installing the trial version of Scheduler according to the Vue 3 instructions. I have managed to connect to the registry but npm is unable to locate a package: "https://registry.yarnpkg.com/@bryntum%2fdemo-resources: Not found".

I followed the instruction to clean the npm cache etc, but at this point there is no node_modules dir not package-lock.json file

Console output (below as text and in attachment as screenshot)
PS G:\Bryntum-4.3.0\examples-scheduler\frameworks\vue-3\javascript\simple> npm config set @bryntum:registry=https://npm.bryntum.com
PS G:\Bryntum-4.3.0\examples-scheduler\frameworks\vue-3\javascript\simple> npm login --registry=https://npm.bryntum.com
npm notice Log in on https://npm.bryntum.com/
Username: andreas.sakellariou..metratek.co.ul
Password:
Email: (this IS public) andreas.sakellariou@metratek.co.uk
Logged in as andreas.sakellariou..metratek.co.ul on https://npm.bryntum.com/.
PS G:\Bryntum-4.3.0\examples-scheduler\frameworks\vue-3\javascript\simple> yarn add @bryntum/grid-vue-3
yarn add v1.22.15
warning package.json: License should be a valid SPDX license expression
info No lockfile found.
warning simple@4.3.0: License should be a valid SPDX license expression
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@bryntum%2fdemo-resources: Not found".
info If you think this is a bug, please open a bug report with the information provided in "G:\\Bryntum-4.3.0\\examples-scheduler\\frameworks\\vue-3\\javascript\\simple\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
PS G:\Bryntum-4.3.0\examples-scheduler\frameworks\vue-3\javascript\simple>

Attachments
brytnum-shot.png
brytnum-shot.png (66.68 KiB) Viewed 470 times

Post by andreas-sakellariou »

---[SOLVED]--- **** Documentation should be updated****

The problem in my case was that I was using Powershell in Windows to perform the (v7 version of) the command:

npm config set @bryntum:registry=https://npm.bryntum.com

Using Powershell the above command inserts the following incorrect entry to the .npmrc file:

=https://npm.bryntum.com

instead of the correct one:

@bryntum:registry=https://npm.bryntum.com

For Powershell to work as expected, you should add double-quotes in the command as follows:

npm config set "@bryntum:registry=https://npm.bryntum.com"

The documentation should be updated to warn about this

Otherwise, standard Command Prompt may be used without changes


Post by mats »

Glad to hear it's resolved and thanks for helping is improve our docs (we'll fix it based on your recommendation).


Post Reply