[ ] The exact fields of the package.json I can help review once you have a sample. name, version, type module, files, exports, repository, homepage, repository, license, keywords, etc.
[ ] - probably index.js file for your exported modules.
[ ] typescript types would be nice, otherwise typescript users will get IDE warnings. you might put claude on that. could do in a future rev too. That's the 'types' field in package.json.
[ ] I'd recommend a test app that uses the published version (e.g. galaxy stars). You can have claude reference the packed version of your npm package locally for manual testing before you publish for quicker turnaround if you want. ask claude about pnpm pack. Once things are working, usually people don't bother to test the packed version ongoing.
[ ] The exact fields of the package.json I can help review once you have a sample. name, version, type module, files, exports, repository, homepage, repository, license, keywords, etc.
[ ] - probably index.js file for your exported modules.
[ ] typescript types would be nice, otherwise typescript users will get IDE warnings. you might put claude on that. could do in a future rev too. That's the 'types' field in package.json.
[ ] I'd recommend a test app that uses the published version (e.g. galaxy stars). You can have claude reference the packed version of your npm package locally for manual testing before you publish for quicker turnaround if you want. ask claude about pnpm pack. Once things are working, usually people don't bother to test the packed version ongoing.