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.
Greenkeeper update broke fang API use
See original GitHub issueI might be wrong about this, but I’m having an issue whereby the output of fang@2.x is inconsistent with the output of fang@1.x, which the code in the config loader relies on.
The config loader relies on a key mode coming back from fang (see https://github.com/frctl/fractal/blob/master/src/core/data.js#L50), but fang no longer returns a mode key, instead going for two possible separate *_mode keys: ace_mode and codemirror_mode.
As such, either the fang dep should be reverted to ^1.0.0 or the code should be updated to use the ace_mode or codemirror_mode key (though it’s worth saying that different languages in fang appear to sometimes not have the codemirror_mode key in v2, ace_mode appears to be consistent, though).
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:7 (2 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
v1.1.7 fixes the fang issue for me.
That’s what I’ve done here so this should fix it.