Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Improve docs with includes list
See original GitHub issueThe maybe toughest thing to get your head around when using TWBS is finding out which files are needed to be included when one wants to use a component. I have just (again) gone through all the hoops with the migration of a build that originally started with v0.4.0-alpha.2 and is now on v0.4.0-beta. Files disappeared, additional ones were necessary and it took me three hours of just finding out what’s missing and what changed.
FYI: This is not a “include CSS and JS from CDN and call it a day”–site, but one that includes only what’s actually in use (by @importing SCSS files, etc.).
Feature request for documentation: Please, add the files needed (SCSS, JS) that make a component work.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sorry, I am not familar with the
scss-docsshortcode you are referring to. Is it the formatting for the docs? In any case, I think comments on the files would already be very helpful by themselves. In fact, I often go and look at each file to figure out the dependencies.If this can be automated, it’d be awesome!