bug: `extTransformsPlugin` is outputting collections css files
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- build-system
Research direction
Start by cloning the linked reproduction and running yarn followed by yarn build; inspect the extTransformsPlugin build path and the referenced stencil.config.ts. Done means the build no longer creates the externalcollection CSS output while preserving the expected dist output.
Written by the indexing model from the issue text.
Description
Prerequisites
- I have read the Contributing Guidelines.
- I agree to follow the Code of Conduct.
- I have searched for existing issues that already report this problem, without success.
Stencil Version
v2.14.2 π
Current Behavior
When building a dist output with a collection dependency, the dependencies css files will be outputted as part of the collection output, however, they appear further up the file tree due to their relative file paths. These css files aren't needed needed for the collection.

Expected Behavior
The css files aren't outputted.
Steps to Reproduce
Clone https://github.com/George-Payne/extTransformsPlugin-bug-reproduction
yarn is being used for workspaces, npm wont work
yarnyarn build
Observe:
collectionconsumer
βββ dist
β βββ cjs
β βββ collection
β βββ collectionconsumer
β βββ esm
β βββ index.cjs.js
β βββ index.js
β βββ loader
β βββ types
βββ externalcollection <------------- This folder should not be outputted
β βββ dist
β βββ collection
β βββ components
β βββ ext-component
β βββ ext-component.css
βββ node_modules
βββ package.json
βββ src
βββ stencil.config.ts
βββ tsconfig.json
Code Reproduction URL
https://github.com/George-Payne/extTransformsPlugin-bug-reproduction
Additional Information
No response
- Dominant language
- TypeScript
- Stars
- 13.1k
- Forks
- 855
- Avg merge
- 4h 7m
- Merged PRs (30d)
- 44
Contributor guide
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.
More from stenciljs/core
-
Stencil v5
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Stencil v5
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Bug: Validated Stencil v5
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Feature: Want this? Upvote it!
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Feature: Want this? Upvote it!
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: π¦ diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 Β·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 Β·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 Β·