Builds Jac projects into PyPI wheels and npm tarballs from jac.toml metadata.
npx skills add https://github.com/PMN123/trapdoor --skill jac-packaging-pmn123
Please help me install this Agent Skill. Skill: jac-packaging Source: https://github.com/PMN123/trapdoor/tree/main/.agents/skills/jac-packaging Command: npx skills add https://github.com/PMN123/trapdoor --skill jac-packaging-pmn123
jac build --as wheel from jac.toml alone, with correct package-directory layout, entry points, extras, and precompiled .jir bytecode collection. - npm publishing: Uses jac build --as npm to compile client modules to ES modules with package.json and .d.ts files, enforcing the pure-client sv-boundary rule. - Pitfall prevention: Catches common failures such as missing package directories, requires_python being silently dropped, string classifiers, and type-check gate rejections. - Use Case: You finished a Jac CLI tool and want it on PyPI. This Skill restructures the project into a package directory, writes a valid jac.toml with console-script entry points, builds the wheel, and uploads it with twine. ## Quick Start Package my Jac project as a wheel with a CLI entry point and publish it to TestPyPI using twine.High-intent search queries and answers about installing and using this skill.
Run `jac build --as wheel` to produce a wheel and sdist from jac.toml, then upload with `twine upload dist/*`. There is no `jac publish` command; test on TestPyPI first with `twine upload --repository testpypi dist/*`.
Run `jac build --as npm` to compile client modules to ES-module JavaScript with a generated package.json and .d.ts files, producing a tarball in dist/. Upload it with `npm publish dist/<name>-<version>.tgz --access public`.
The wheel build only collects a package directory whose name matches project.name in jac.toml; single top-level .jac files are never collected. The default `jac create` template puts main.jac at the root, so you must create a matching package directory yourself.
No. jaclang is not a PyPI package; it is the host runtime supplied by the jac binary that runs your wheel. Consumers install your package with `jac install <pkg>` inside a jac-managed project, not a bare pip install.
jac build runs the whole-program type-check gate first and refuses to emit an artifact on failure. Fix the reported diagnostics, or pass `--no_typecheck` to skip the gate as a last resort.
No. A module with an sv import or call crosses a server boundary and the npm build fails, since npm packages must be pure client code. Keep server-coupled code in your application rather than the published library.
nihalnihalaniScaffolds new Jac projects with jac create kinds, templates, and post-scaffold verification.
nihalnihalaniBuilds Jac projects into PyPI wheels and npm tarballs from jac.toml metadata.
nihalnihalaniConfigure npm package imports and React refs in Jac client components.
nihalnihalaniMaps Jac project kinds to build verbs and the guides to load.