Do not run yarn build during postinstall hook

[ranyitz]

Maybe I'm missing something, but running build during postInstall doesn't seem to be the right way to go.

This PR moves it into pretest instead.

Fixes #263

[SimenB]

Not what I want, but merging to fix the issue

[SimenB]

Thanks, and sorry about this!

I don't wanna build before every test run, but I'll figure something out :)

[swissspidy]

I thought that's what 9f40d2c should do?

[SimenB]

I don't want to build before every test run, since it'll slow things down.

I'll probably add build to ci, and throw explicit error from eslintrc. But I'm currently in line to board a plane to Paris for react-europe, so this seems like a great quickfix in the meantime :)

[swissspidy]

Oh, sorry, I misread. Thanks for clarification! Enjoy the conference 🎉

[ranyitz]

@SimenB I agree that this is not a good solution for the long term. Thanks for merging :)

[SimenB]

🎉 This PR is included in version 22.6.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[SimenB]

I think using prepare is the correct lifecycle hook, right?

[ranyitz]

@SimenB It may be, but it still doesn't solve the local development problem.

I think we should go with adding a yarn build step in our travis configuration (for CI flow)

And for local development, we should create a watch script that runs babel/tsc on every change. prepare would run the build locally after the first install but it won't be much fun running yarn build after each change. (while running jest --watch on a different terminal)

What do you think?