Development guidelines

@tricoder42 can you provide some guidelines on how to setup environment and work on the lib?

Right now we have Contributing guidelines but it’s not enough info there.

For example when taking step 3. yarn test, test fails with multiple errors Could not locate module @lingui/conf... because it hasn’t been built and there’s no info how to build it. I see scripts/build/ directory and can guess that it’s what should be run beforehand but there’s no info which file tor run etc.

What I’d like to see is the list of steps needed from cloning the lib to setting up everything so that one can modify, build and link it to an existing project in order to be able to test it.

I think such guidelines will help people who want to contribute a lot.

[tricoder42]

Hey @snegostup, I’ve just mentioned it in contributing docs. You need to run yarn release:build (shortcut for node ./scripts/build/) manually.

I always create a unit test for all I need, because unit tests run in watch mode. I use yalc only as a final check in local project.

[vsnig]

@tricoder42 thanks! That’s what I needed. Do you manually rebuild after change or is there a way to make it watch for changes and automatically rebuild?