|
15 | 15 |
|
16 | 16 | - **Missing exports:** Suppose the **awesome-widgets** package exports an API function `AwesomeButton.draw()` that requires a parameter of type `DrawStyle`, but you forgot to export this enum. Things seem fine at first, but when a developer tries to call that function, they discover that there's no way to specify the `DrawStyle`. How to avoid these oversights? |
17 | 17 |
|
18 | | -- **Accidental exports:** You meant for your `DrawHelper` class to be kept internal, but one day you realize it's a package export. When you try to remove it, consumers complain that they are using it. How do we avoid this in the future? |
| 18 | +- **Accidental exports:** You meant for your `DrawHelper` class to be kept internal, but one day you realize it's being exported. When you try to remove it, consumers complain that they're using it. How do we avoid this in the future? |
19 | 19 |
|
20 | | -- **Alpha/Beta graduation:** You want to release previews of new APIs that are not ready for prime time yet. But if you did a major SemVer bump every time you change these definitions, the villagers would be after you with torches and pitchforks! A better approach is to designate certain classes/members as **alpha** quality, then promote them to **beta** and finally to **public** when they're mature. But how to indicate this to your consumers? (And how to detect scoping mistakes? A **public** function should never return a **beta** result.) |
| 20 | +- **Alpha/Beta graduation:** You want to release previews of new APIs that are not ready for prime time yet. But if you did a major SemVer bump every time these definitions evolve, the villagers would be after you with torches and pitchforks! A better approach is to designate certain classes/members as **alpha** quality, then promote them to **beta** and finally to **public** as they mature. But how to indicate this to your consumers? (And how to detect scoping mistakes? A **public** function should never return a **beta** result.) |
21 | 21 |
|
22 | | -- **\*.d.ts rollup:** You webpacked your library into a nice **\*.js** bundle file -- so why are you distributing your typings as a messy tree of **lib/\*.d.ts** files full of private definitions? Let's consolidate them into a tidy **\*.d.ts** rollup file. If you publish internal/beta/public releases, a semantic analyzer can trim the **\*.d.ts** rollup according to each release type. Developers working on a production project don't want to see a bunch of **internal** and **beta** members in their VS Code IntelliSense! |
| 22 | +- **\*.d.ts rollup:** You webpacked your library into a nice **\*.js** bundle file -- so why ship your typings as a messy tree of **lib/\*.d.ts** files full of private definitions? Can't we consolidate them into a tidy **\*.d.ts** rollup file? And if you publish internal/beta/public releases, each release type should get its own **\*.d.ts** file with appropriate trimming. Developers building a production project don't want to see a bunch of **internal** and **beta** members in their VS Code IntelliSense! |
23 | 23 |
|
24 | | -- **Online documentation:** You have faithfully annotated each TypeScript member with nice [JSDoc](http://usejsdoc.org/) descriptions. Now that your library is published, you should probably set up [a nicely formatted](https://docs.microsoft.com/en-us/javascript/api/sp-http) API reference. Which tool should we use to generate that? (What!? There aren't any good ones!?) |
| 24 | +- **Online documentation:** You have faithfully annotated each TypeScript member with nice [JSDoc](http://usejsdoc.org/) descriptions. Now that your library has shipped, it's time to set up [a nicely formatted](https://docs.microsoft.com/en-us/javascript/api/sp-http) API reference. What tool to use? |
25 | 25 |
|
26 | 26 | **API Extractor** provides an integrated, professional-quality solution for all these problems. It is invoked at build time by your toolchain and leverages the TypeScript compiler engine to: |
27 | 27 |
|
28 | 28 | - Detect a project's exported API surface |
29 | 29 | - Capture the contracts in a concise report designed to facilitate review |
30 | 30 | - Warn about common mistakes (e.g. missing exports, inconsistent visibility, etc.) |
31 | | -- Generate \*.d.ts rollups |
32 | | -- Output API documentation in a portable format that's easy to integrate with your publishing pipeline |
| 31 | +- Generate \*.d.ts rollups with trimming according to release type |
| 32 | +- Output API documentation in a portable format that's easy to integrate with your content pipeline |
33 | 33 |
|
34 | 34 | Best of all, **API Extractor** is free and open source. Join the community and create a pull request! |
35 | 35 |
|
|
0 commit comments