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.
Move TypeScript definitions to DefinitelyTyped
See original GitHub issueTypeScript is gaining more and more traction these days, now publishing type definitions on npm as @types/package-name. @ai, if you still want to remove the TS definitions from this project, I can submit a PR to DefinitelyTyped and it will be published at https://www.npmjs.com/package/@types/postcss in the future; however, that is definitely not the golden path and I would urge you to reconsider based on how much traction TypeScript is getting these days.
Issue Analytics
- State:
- Created 7 years ago
- Comments:15 (15 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
There are no postcss types on DefinitelyTyped; therefore, no
@types/postcsspackage on npm, “because” thepostcsspackage supplies them out-of-the-box; thus, there is no need. This is the golden path so I’m pretty happy about it.What I’m saying is that if someone noticed something missing from
postcss#postcss.d.ts, all they would need to do is submit a PR to this repo to update them. Problem solved.OK, let’s keep them inside if we have no good solution right now.
BTW, one file difintion is very good change 😃.