fix(ast): fix wrong node type on literal expressions

[g-plane]

Same as eslint/typescript-eslint-parser#509

Fix #8

[JamesHenry]

Apologies, @g-plane, I suddenly realised I hadn't been checking the commit format. I have now set up linting for it, it should follow the conventional changelog style:

type(scope?): subject
body?
footer?

This is because I release automatically using semantic-release.

Please could you update your commit message?

[g-plane]

Maybe I just need to update the PR title? Then, you can squash and merge it.

[JamesHenry]

I really appreciate the quick response (caught me a little off guard how prompt you were! :D ), I have since added formatting with prettier to the repo.

Both the formatting and the commit messages are checked as part of the build now. I would feel more comfortable getting everything up to date and having a passing build before merging please.

Also please remember to add the BREAKING back in the commit body, in this commit style it is not represented in the subject, it is in the commit body.

You can use the cz npm script to use an interactive prompt to build the commit message too just FYI

[JamesHenry]

Sorry again that I made extra work for you on this

[g-plane]

No problem and I will do it later.

[g-plane]

@JamesHenry Updated.

[JamesHenry]

Thanks again @g-plane!

[JamesHenry]

🎉 This PR is included in version 3.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀