Regenerate compiled files on yarn/npm reinstall

[danielkcz]

Replacement for PR #60 (somehow I messed up rebase).

[changeset-bot]

🦋 Changeset detected

Latest commit: a79de91

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
xstate-codegen	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[mattpocock]

@FredyC Carrying on conversation here.

My work uses a yarn workspaces monorepo. When I run xstate-codegen inside package-name, then add a new package at root, the package-name/node_modules/@xstate/compiled folder is removed, but the codegen does not re-run.

What can be changed to make sure this case is picked up?

[danielkcz]

@mattpocock I am not sure I understand your use case. You are not running xstate-codegen in the root?

I mean there isn't really anything magical about this solution. It simple uses getTargetDir() to find generated package.json file and when that gets deleted, it will write all generated files again. Watching over the whole folder wasn't working for some reason.

[mattpocock]

@FredyC OK - that makes sense. I'll see if I can get it working for my use case.

You are not running xstate-codegen in the root?

Correct. There is a node_modules folder at the root and a node_modules folder inside package-name. I'll investigate more.