Compile workflows even when not used anywhere
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 365
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 169
Description
I would like to have the workflows all compiled even when I haven't imported and used them anywhere (context: I want to dynamically import instead). I tried to include them in the package.json's sideEffects but that doesn't seem to work. Is there something in the build script that prevents it?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the build script and package.json, especially the sideEffects configuration, and reproduce the behavior with a workflow that is never imported. Trace why unused workflows are omitted and determine what compilation behavior is needed for dynamic imports. Done means unused workflows are compiled and remain dynamically importable, with coverage for that case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100