Refactor

[tommy-mitchell]

Per the discussion in https://github.com/sindresorhus/meow/pull/230#issuecomment-1483644249, this is a tracker issue for a general refactor:

• [x] Target Node 14 and update dependencies (#234)
• [x] Separate index.js into separate source files (#234)
  • Separate tests into smaller files/fixtures, maybe consolidate via macros
  • Not directly related, but adding subcommands (#69) benefits from this
• [x] Target Node 16 and use new features (#235)
• [x] Bundle dependencies (#67, #242)
• [ ] Ensure that documentation / terminology is consistent across the project
  • Improve error messages - consistent format, make sure all cases are covered
  • Potentially add JSDoc comments to source functions
• [ ] Look into lazy loading cli.pkg (#104)
• [ ] Add tests where missing, if needed
• [x] Improve documentation surrounding importMeta (#260)
  • ~The readme doesn’t say that it’s required (https://github.com/sindresorhus/meow/issues/222#issuecomment-1627530219)~
• [ ] Rewrite in TypeScript (#252)

[tommy-mitchell]

I also think a rewrite in TypeScript would be beneficial from an ease-of-development perspective. I'd be happy to make a PR, but I understand not wanting to go that route.

[sindresorhus]

The main reason I usually don't want TypeScript is that it introduces a build-step. If - Bundle dependencies ends up requiring a build-step, it may make sense to move to TypeScript.

[sindresorhus]

@tommy-mitchell Should we release a new major version or do you intend to work on more items here?

[tommy-mitchell]

@sindresorhus sorry for the late response, I’ve been busy with work this past week. Probably not going to have much more time for another week or two, so I think we could release now and add e.g. subcommands in a minor version

[tommy-mitchell]

@sindresorhus thoughts on moving to TypeScript, now that we have a build step? We can use Rollup to emit the built JavaScript, and since a build is generated before testing, we can use tsd on the built index.d.ts.

[sindresorhus]

👍