Launch Week Day 5: Introducing Reachability for PHP.Learn More
Socket
Book a DemoSign in
Socket

@codama/renderers-js

Package Overview
Dependencies
Maintainers
1
Versions
46
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@codama/renderers-js

JavaScript renderer compatible with the Solana Kit library

latest
Source
npmnpm
Version
2.2.0
Version published
Maintainers
1
Created
Source

Codama ➤ Renderers ➤ JavaScript

npm npm-downloads

This package generates JavaScript clients from your Codama IDLs. The generated clients are compatible with @solana/kit.

Installation

pnpm install @codama/renderers-js

Usage

Add the following script to your Codama configuration file.

{
    "scripts": {
        "js": {
            "from": "@codama/renderers-js",
            "args": ["clients/js"]
        }
    }
}

The first argument is the package folder — i.e. where the package.json lives. The generated files will be written to src/generated within that folder by default.

An object can be passed as a second argument to further configure the renderer. See the Options section below for more details.

Options

The renderVisitor accepts the following options.

NameTypeDefaultDescription
deleteFolderBeforeRenderingbooleantrueWhether the base directory should be cleaned before generating new files.
formatCodebooleantrueWhether we should use Prettier to format the generated code.
generatedFolderstring'src/generated'The path to the generated folder relative to the package folder.
prettierOptionsPrettierOptions{}The options to use when formatting the code using Prettier.
asyncResolversstring[][]The exhaustive list of ResolverValueNode's names whose implementation is asynchronous in JavaScript.
customAccountDatastring[][]The names of all AccountNodes whose data should be manually written in JavaScript.
customInstructionDatastring[][]The names of all InstructionNodes whose data should be manually written in JavaScript.
linkOverridesRecord<'accounts' | 'definedTypes' | 'instructions' | 'pdas' | 'programs' | 'resolvers', Record<string, string>>{}A object that overrides the import path of link nodes. For instance, { definedTypes: { counter: 'hooked' } } uses the hooked folder to import any link node referring to the counter type.
dependencyMapRecord<string, string>{}A mapping between import aliases and their actual package name or path in JavaScript.
dependencyVersionsRecord<string, string>{}A mapping between external package names — e.g. @solana/kit — and the version range we should use for them — e.g. ^6.0.0. The renderer offers default values for all external dependencies it relies on but this option may be used to override some of these values or add new ones.
internalNodesstring[][]The names of all nodes that should be generated but not exported by the index.ts files.
nameTransformersPartial<NameTransformers>{}An object that enables us to override the names of any generated type, constant or function.
nonScalarEnumsstring[][]The names of enum variants with no data that should be treated as a data union instead of a native enum type. This is only useful if you are referencing an enum value in your Codama IDL.
renderParentInstructionsbooleanfalseWhen using nested instructions, whether the parent instructions should also be rendered. When set to false (default), only the instruction leaves are being rendered.
kitImportStrategy'granular' | 'preferRoot' | 'rootOnly''preferRoot'Whether to generate imports from granular packages (e.g. @solana/addresses, @solana/codecs-strings) or from the @solana/kit package. 'granular': always use granular packages when available. 'preferRoot' (default): use @solana/kit when the symbol is exported from it; otherwise fall back to granular packages. 'rootOnly': only import from the @solana/kit package. This may use @solana/kit subpath exports (e.g. @solana/kit/program-client-core). This is useful when installing @solana/kit as a peerDependency, but may require TypeScript moduleResolution: "bundler".
syncPackageJsonbooleantrueWhether to update the dependencies of the existing package.json — or create a new package.json when missing — inside the package folder.

Keywords

solana

FAQs

Package last updated on 20 Apr 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts