https://github.com/agilgur5/rpt2-repro
A minimal reproduction environment for issues with rollup-plugin-typescript2: https://github.com/ezolenko/rollup-plugin-typescript2
https://github.com/agilgur5/rpt2-repro
rollup rollup-plugin rollup-plugin-typescript2 ts typescript typescript-library
Last synced: 27 days ago
JSON representation
A minimal reproduction environment for issues with rollup-plugin-typescript2: https://github.com/ezolenko/rollup-plugin-typescript2
- Host: GitHub
- URL: https://github.com/agilgur5/rpt2-repro
- Owner: agilgur5
- Created: 2022-06-08T18:14:18.000Z (about 4 years ago)
- Default Branch: master
- Last Pushed: 2023-07-14T03:55:43.000Z (almost 3 years ago)
- Last Synced: 2025-02-28T20:38:18.643Z (over 1 year ago)
- Topics: rollup, rollup-plugin, rollup-plugin-typescript2, ts, typescript, typescript-library
- Language: JavaScript
- Homepage: https://stackblitz.com/edit/rpt2-repro
- Size: 16.6 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# rpt2-repro
A minimal reproduction environment for issues with [rollup-plugin-typescript2](https://github.com/ezolenko/rollup-plugin-typescript2)
Please do your best to create a [minimal example](https://stackoverflow.com/help/minimal-reproducible-example) that reproduces this behavior.
Minimal reproductions help us find the root cause of an issue much more expediently than trying to interpret and disentangle a complicated repo. The process of creating a minimal reproduction also often helps users find a misconfiguration in their code. It could also help you identify the root cause yourself and potentially create a Pull Request to fix it!
## Usage
1. Find this environment on [StackBlitz](https://stackblitz.com/edit/rpt2-repro)
1. Click "Fork"
1. Add your deps in `package.json` and run `npm install` in the terminal
1. Add your configuration in `tsconfig.json` and `rollup.config.js`
1. Modify `src/index.ts` to provide a minimal example of the problem you have run into
1. Run `npm run build` and make sure you can reproduce the problem
- If you cannot reproduce this problem minimally, the issue may be due to misconfiguration (and would therefore not be a bug in rpt2)
1. Can run `npm run tsc` to double-check that `tsc` does not have the same problem
- If `tsc` has the same problem, then it is very possible the issue is in TypeScript itself
1. Click "Share" and copy the link into the issue that you are filing
1. Make sure to **follow the steps** in the issue template