David Smith
David Smith
My suggestions: 1. Fix the `yarn unlink` code so it doesn't tell people to do something that doesn't work. 1. In the first paragraph of the `yarn unlink` doc page,...
@cpetzel Now that xstate v4 includes its own interpreter, you might be better off without xstateful. Do you have a use case that xstate v4 doesn't cover but xstateful does?
Please keep this open. It’s still an issue. It would be great to have some testing guidance in the documentation if nothing else.
*keepalive packet*
To expand on the second question. Consider this `_app.js`: ```js // _app.js import React from 'react'; const App = props => { const { render } = props; return (...
I think those steps would probably solve all the major concerns I have right now. The key for me is to have (officially blessed) access to an unstyled base that...
Instant reaction: I tried mdx with next.js a couple of weeks ago. I found that an mdx page couldn't import a component defined with flow types: the imports failed due...
Good idea. I'll take a look, thanks.
I've hit this issue in my project, which doesn't deploy built packages to any npm registry and so doesn't need `@semantic-release/npm`. It's a problem for me because `@semantic-release/npm` has a...