ui build process - standard way to expose

[davidmarkclements]

How ui does its build its up to integration - but for development (watching, rebuild cycle) and deployment (ci, prod ui build) we should think about a standard way to expose the components build process so that deployment and development tools can work without config across projects

[piccoloaiutante]

aren't npm scripts enough expose build process @davidmarkclements ?

[mihaidma]

for the moment we have webpack and npm scripts. For production there is some work done with Drone on the previous boilerplate project, don't know yet if the build and deployment systems will be added to the next planning.

[davidmarkclements]

webpack is just.. the worst.

but I feel that I've not got my point across for this issue, here's how I see things

• the boilerplate shouldn't be intrinsically coupled to any UI approach
• the fact that we're using react for the initial boilerplate is purely incidental
• the choices made for the frontend build process are relative to the framework etc.
• since we don't want to actually couple anything to the paradigms or methods of the frontend we need a standardize way to trigger a frontend build, in a production and development scenario

@piccoloaiutante is right, npm scripts should cover this, but we need to define and standardize what those scripts are

npm run build for dev and npm run build --production should work?

So if we use webpack (or... preferably browserify), or whatever we use, it should be initialised with the same npm script