Richard Laffers

@tmjam Does this not work for you? ``` const { query } = useQuery(action, false); // elsewhere in your component in an async function: const response = await query() ```

Thank you for your report. This should be fixable easily.

:tada: This issue has been resolved in version 1.0.2 :tada: The release is available on: - [npm package (@latest dist-tag)](https://www.npmjs.com/package/eslint-plugin-xstate/v/1.0.2) - [GitHub release](https://github.com/rlaffers/eslint-plugin-xstate/releases/tag/v1.0.2) Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:

Yes, that is to be expected. Since the machine configuration is just a plain JS object, we have no way of knowing it is going to be used as an...

Unfortunately, I'm quite busy in the next few days so there will be no quick solution. I plan to look into how type-aware linting rules can be created and whether...

Yes indeed, that would be a workaround. @skyFabioCozz Try adding a comment to your file with machine configuration: ```javascript /* eslint-plugin-xstate-include */ ```