![\"Logo\"](\"https://i.imgur.com/MsQMjew.png\")
\n \n
\n standard-pkg • Build strict, ES2019 distributions from your project.\n
\n\n- 🗓 Updates yearly with the latest ECMAScript spec.\n- ⚡️ Powered by Babel; Automatically includes any custom/experimental plugins found in your babel config.\n- 📦 Used internally by most [@pika/pack](https://github.com/pikapkg/pack) build pipelines.\n\n```\n$ npm install -g standard-pkg\n$ standard-pkg --src src/ --dist lib/\n » Building src/ → lib/...\n » Linting lib/...\n ✓ 0 issues found.\n```\n\n\n## Why?\n\n### Lint Your Package to Strict ES2019 Spec\n\n```\n$ standard-pkg --dist lib/\n » Linting lib/...\n ⚠️ [lib/index.js 2:0] Imported file does not exist.\n Missing file extension for import \"./some/import\".\n ✘ 1 issues found.\n```\n\n\n### Publish Modern JavaScript With Your Package\n\n```json\n{\n \"scripts\": {\"build\": \"standard-pkg --src src/ --lib lib/\"},\n \"esnext\": \"lib/index.js\"\n}\n```\n\n\n### Use Existing Tools with Experimental Language Features\n\nStandard-pkg builds to a standard language target for other tooling to consume (or to publish directly with your package). This is especially useful if you're using TypeScript or experimental language features that your tooling may not support.\n\n\n## Exceptions\n\nWhile we try to match the ES2019 spec as strictly as possible, the following exceptions are required to support some common use-cases where no other workaround exists:\n\n1. Supports bare module specifiers: This is the npm standard, and modern tooling like bundlers support it.\n1. Supports dynamic `import()`: This is a [stage 4 proposal](https://github.com/tc39/proposal-dynamic-import) which allows dynamically importing modules.\n1. Supports `import.meta.url`: This is a [stage 3 proposal](https://github.com/tc39/proposal-import-meta) which allows modules to read their location (filepath or URL).\n","readmeFilename":"README.md","description":"