argyleink / argyleink/open-props
Offer a scoped option
- Dominant language
- HTML
- Stars
- 5.5k
- Forks
- 216
- PR merge metrics
- No merged PRs in 30d
Description
I often work on SPA starter templates. To keep package.json dependencies light, I use CDN for the bundled examples.
Unfortunately when using `Open Props` this leaves me with two options.
1. **CDN** - The styling bleeds into the user's code.
2. **NPM** and `node props.js '' true '.starter-examples'` - This adds dependencies to package.json that the user might not want.
If Open Props had a scoped CDN option, like `where(.open-props)`, it would be very simple to keep the project lean while styling specific elements without bleeding into the user's code.
---
Thanks for a great library!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the `node props.js '' true '.starter-examples'` entry point and how the CDN bundle is produced. Compare the current global CDN behavior with the requested `.open-props` scope, and verify that the result styles only scoped elements without adding unwanted package.json dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, node.js
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100