|
1 | 1 | # JITI ISSUES |
2 | 2 |
|
| 3 | +## Issue Discovery Workflow |
| 4 | + |
| 5 | +When encountering a module loading error with jiti/tsx, follow this systematic approach to identify the problematic package: |
| 6 | + |
| 7 | +1. **Isolate the issue** |
| 8 | + |
| 9 | + - Open `code-pushup.config.ts` |
| 10 | + - Comment out all plugin configurations |
| 11 | + - Run: `nx code-pushup --print-config --output out.json` |
| 12 | + - Verify the command succeeds without errors |
| 13 | + |
| 14 | +2. **Identify the problematic plugin** |
| 15 | + |
| 16 | + - Uncomment plugins one at a time |
| 17 | + - After each plugin, run: `nx code-pushup --print-config --output out.json` |
| 18 | + - Continue until the error reproduces |
| 19 | + - The last plugin uncommented is the one causing the issue |
| 20 | + |
| 21 | +3. **Document the issue** |
| 22 | + - Once the problematic plugin is identified, collect all relevant information |
| 23 | + - Fill out the issue template below with: |
| 24 | + - The library/package name |
| 25 | + - Error message and stack trace |
| 26 | + - Reproduction steps |
| 27 | + - Source code locations |
| 28 | + - Any preliminary fixes or workarounds |
| 29 | + |
| 30 | +- add the issue to the list of issues below |
| 31 | + |
3 | 32 | ## Issue Template |
4 | 33 |
|
5 | 34 | **Library** (required) |
@@ -30,7 +59,13 @@ Links to a file, a snippet or a PR with the fix |
30 | 59 | Local files are preferred. |
31 | 60 | Location of the file: `tools/jiti/<library-name>/fix-<library-name>.ts` |
32 | 61 |
|
33 | | -## Issues |
| 62 | +## List of Issues |
| 63 | + |
| 64 | +### My Issue |
| 65 | + |
| 66 | +... |
| 67 | + |
| 68 | +## Old Issuess for reference |
34 | 69 |
|
35 | 70 | ### axe-core |
36 | 71 |
|
|
0 commit comments