New build process

[vforge]

• Move all the source files to source directory.

• Update READMEs everywhere.

• For now (until we have private npm account or artifactory) we cannot publish the package, so the output files need to stay in this repo.

• I do not want the client to download X libraries that are not needed in order to use the RDS (like Ember is needed for the DS itself), so the process is compiling all the files into ES5 and you only need React, ReactDOM and PropTypes in order to use them. The client shouldn't care if an RDS component needs lodash or anything else.

• For the reason above I do not want to have a post-install process. In the future, the build should happen only before the package is published.

NOTE: This PR does not contain build files, because I wanted it to be easier to read. Once it's clear, I'll add the result of yarn build.

[coveralls]

Pull Request Test Coverage Report for Build 431

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 411:	0.0%
Covered Lines:	250
Relevant Lines:	250

---

💛 - Coveralls

[JoshuaRogan]

I think nearly all of these files should be generated on prepublishOnly or something similar. It makes it very hard to write code with all of this extra code.

[mklucsarits]

Is all this extra code auto-generated?

[vforge]

yes!

[mklucsarits]

@v Can you explain a bit more what's going on here? Like what the extra code is doing and how it's generated?

[vforge]

@JoshuaRogan Unfortunately because of our licensing we won't publish this package to npm.js. There are other ideas floating around, but for now everything stays on GH.

@mklucsarits Sure, let me add READMEs and some description during the weekend and we'll get back to this PR next week.

[JoshuaRogan]

I believe you can run it during npm install without it being on npm. https://docs.npmjs.com/misc/scripts

[vforge]

Don't use install. Use a .gyp file for compilation, and prepublish for anything else. You should almost never have to explicitly set a preinstall or install script. If you are doing this, please consider if there is another option. The only valid use of install or preinstall scripts is for compilation which must be done on the target architecture.

https://docs.npmjs.com/misc/scripts#best-practices

[vforge]

I'll in the process of updating docs/readmes so it's clear why it's like that right now.

[vforge]

@mklucsarits and @JoshuaRogan I've updated PR and added a description. Hopefully, it's clearer now.

[vforge]

@mklucsarits automated dismiss, sorry about that!

I turned it off

[JoshuaRogan]

@vforge Can we use artifactory to host the content? It really sucks having the build files in the repo.

[vforge]

@JoshuaRogan I'll work on that.