Creating a toolkit - preferred to be done from arcade-ai repo?

[amurauyou]

Hi team. I started development of a new toolkit from a completely separate repo, not from within arcade-ai.
When I ran skaffolding with arcade new it then put arcade-ai, arcade-serve and arcade-tdk as local paths into pyproject.toml - so technically it expect a specific development environment.

Is that a not supported / not recommended approach? What would be the one?

[amurauyou]

Repo reference: https://github.com/amurauyou/arcade-polygon-toolkit

[byrro]

Hey @amurauyou, there's no dev command in the Arcade CLI. I believe you meant arcade new, am I right?

[amurauyou]

Yes, arcade new. Updated it.

[torresmateo]

Hi @amurauyou

The recommendation depends on whether you plan to contribute the toolkit to Arcade. If so, yes, you should start from within the arcade-ai repo, and we hope it will result in a PR when you're done!

If you simply need to build a toolkit and you don't plan to contribute it to Arcade, you can do it from anywhere else. In fact, arcade new will have a slightly different behavior when run from arcade-ai/toolkits (you get an extra question asking whether the toolkit is meant as a community contribution, as well as extra files, if you say "yes"). In this section of my tutorial you can see me talk about it!

[amurauyou]

Thanks @torresmateo

you get an extra question asking whether the toolkit is meant as a community contribution, as well as extra files, if you say "yes"
I didn't have that question asked. I ran arcade new through uv dependency (uv tool run --from arcade-ai arcade new my-new-toolkit) - could this mean that the one in PyPI doesn't have that question yet?

[byrro]

You can have your toolkit separately from the arcade-ai repo. In that case, simply omit the sources in the toml file. If you're using uv, you should add --no-sources, e.g. uv sync --active --all-extras --no-sources. We understand this is a bit confusing and are working on an improvement to the arcade new dev experience.

In case you'd like to contribute to the arcade-ai repo and make your toolkit available to other Arcade users, you'd need to send a PR and the toolkit will go through our internal review. If you intend to contribute to arcade-ai, let us know beforehand so that we can give you some guidance on the toolkit implementation.

[amurauyou]

Thanks @byrro.

Yes, that's what I did - as I was starting a toolkit in a separate repo - I had to disable the local mapped sources that were appended with arcade new and install add those dependencies manually with uv add.

I'm just highlighting that the two separate paths for developing the toolkit were not as explicitly maintained and communicated in the docs, which led to confusion. I'd recommend explaining the two paths in the docs:

• for toolkits intended for contribution into the actual arcade-ai repo - extend the contribution guidelines (https://github.com/ArcadeAI/arcade-ai/blob/main/CONTRIBUTING.md)
• for toolkits developed outside of the arcade-ai repo - clean guidelines in docs and updated arcade new

[evantahler]

@amurauyou please help us out! https://github.com/ArcadeAI/docs holds our docs