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.
Broken compatibility with Google Closure Compiler
See original GitHub issue1.0.0 breaks compatibility with Google Closure Compiler. I think this is unfortunate to break not only GCC users but whole ClojureScript community as well. It is failing on export * from ... syntax in index.js files, because it’s not supported in GCC. Is it possible to not use imports from /index modules and instead to be explicit what concrete module (eg. /component) is actually imported? I tested it by hand editing package files and it works again. I hope this will also help with tree-shaking for other consumers of this amazing library.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (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
As per my knowledge, PR #4594 by @moog16 fixes this issue.
That’s a good point. We purposely avoid referencing index from foundations/adapters for the sake of wrapper libraries which shouldn’t need index or the component, but we allowed referencing index from components under the assumption that if you’re using it in the context of vanilla MDC Web, there shouldn’t be an issue.
So I guess avoiding referencing index from component files is a third option.