Log in to Retool via API: 'retool-ccl@*' is not in this registry

I am trying to setup my first custom component library and cannot login as per the documentation.

Using the command:

npx retool-ccl login

I am getting the following error (in VS Code):

new-custom-component> npx retool-ccl login
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/retool-ccl - Not found
npm error 404
npm error 404  'retool-ccl@*' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.

Is there an updated command to login or do I need to do something else?

I did a quick search at npmjs.com and couldn't find retool-ccl.

Hey @Shawn_Optipath!

Make sure you run npm install before trying to log in. That should fix it but let me know if you run into the same issue afterwards.

Hey @Darren!

Yes, I ran npm install before. I tried it again just to make sure and npm is there. See the image below.

Setting this up now because I still haven't found a solution to my custom component to display a Google Map. Would love to get that going if you have a minute over here.

I'll hop over there for the time being to hopefully get you unstuck, as this was primarily a workaround if I remember correctly. :+1:

Correct, this is a workaround. As custom components is deprecated, I'll be need to go down this path regardless. The other topic is definitely the priority. Thanks!

For when you come back to this, it looks like there's something wonky with your npm setup. Running npm install should look more like the following:

Note the number of packages, in particular. This is going to sound silly, but can you double check that you're running the command in the correct directory? You might also want to check the npm version - I'm on 10.8.2, for context.

Im still running into this issue when trying to make my own custom components. Im on the latest version of npm and node. Still getting the exact same error.

1 Like

Hey @Gouled_Jeelal! Welcome to the community. :slightly_smiling_face:

Can you share the specific console output that you get after running npm install && npx retool-ccl login?

hey @Darren, I cannot get this Custom Component to run. Been back and forth and need help. Following this article Getting started with custom component libraries | Retool Docs but does not really work. Any suggestions are appreciated

i tried applying the npm audit force, but that just gives me more errors, as once updated this line in index.tsx tells me Retool is not recognized

image

Hi @Inno_uchile.cl! Thanks for reaching out.

To start, you don't need to worry about any deprecation messages that you see after running npm install. Running npm audit fix can actually break the package's dependencies.

I'm pretty sure the original error that you're seeing is the result of passing extraneous arguments via the npx retool-ccl init command.

Straight to the point, I love it! You are right. Somehow the first time I ran npx retool-ccl init i got the /? result, a list of arguments and how to use them, and i defined the arguments for a command line.

Today, i tried again the init without the arguments and i got asked about the name of the project and the description. And after completing those steps it seems to be working. At least those errors are gone. Thanks!

1 Like

Hi sorry for the late reply. One of the things that helped was git cloning the template repository and seemed to work fine afterwards.

I do have another question. After I make my changes and deploy my new component, it should reflect immediately right? I'm having instances where the development environment looks different from prod release.

Yes, you should typically see the changes reflected in the Retool UI almost immediately. In order for your dev version to update, though, you need to be running npx retool-ccl dev via your local dev environment.