npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

build-front-container

v0.1.0

Published

[![Build Status](https://travis-ci.org/alfa-bank-dev/build-front-container.svg?branch=master)](https://travis-ci.org/alfa-bank-dev/build-front-container)

Downloads

5

Readme

Build front container module

Build Status

Warning! build project inside container works very slow with docker-machine on Mac.

The main goal of this project is to uniform the process of building web applications. We heavily use Docker in our build process. We can divide the build process into two stages:

  • create all the required artifacts. Mainly, they're some JS and CSS bundles, images, etc.
  • build Docker image using the artifacts from the previous step

We recommend creating artifacts in the specially prepared docker-container. Although, you can build you artifacts on the host, but building project inside container has some benefits:

  • your project created in the suitable environment. So the versions of tools are correct - node.js, npm and friends.
  • sometimes it's not possible to get the right tools on the CI-server

The first stage requires build.sh script. You can use already prepared scripts(see ./build-scripts) or you can put your own one. So this bash script will run inside docker container and in the end, we'll get some files.

Then we need to put these files into container. For this purpose, two archives create:

  • app.tar.gz - application files
  • public-modules.tar.gz - for npm-deps

And then just put them inside the image(see Dockerfile).

It's better not to add the build-front-container module to the package.json as a dependency. But install it manually before build.

Options

See output from

./node_modules/.bin/build-front-container --help

How to use

Add command to your npm-scripts. E.g.:

$ grep scripts -A 1 package.json
  "scripts": {
    "build-front-container": "build-front-container",

By default all artifacts will be put into .build directory. It's also possible to specify output directory. E.g.:

$ grep scripts -A 1 package.json
  "scripts": {
    "build-front-container": "build-front-container --output-dir .build-xxx",

You can specify what build script to use for building project. E.g.:

$ grep scripts -A 1 package.json
  "scripts": {
    "build-front-container": "build-front-container --build-script-path ./build.sh"

You can choose one of predefined build scripts. E.g.:

$ grep scripts -A 1 package.json
  "scripts": {
    "build-front-container": "build-front-container --project-type webpack"