Steve Springett stevespringett

I am in the process of introducing single page applications to where I work. For development, using node based build tools is much easier for the single page applications. However, the build process for our organization is based upon maven. Our solution started with the maven plugin frontend-maven-plugin. It worked great at first, but then we ran into a situation that I couldn't make work with it.

As stated before, at our organization, we have the older ecosystem which is maven and the newer ecosystem which is node. Our goal was to keep the hacking to a minimum. We did this by putting all of the hacks into a single super node based build file. This is what maven calls and the reason frontend-maven-plugin wasn't sufficient. The super node based build script calls all of the other build scripts by spawning npm run. Try as I might, I could not figure out how to make the spawn work. front-end-maven-plugin downloads npm

People

`:bowtie:`	😄 `:smile:`	😆 `:laughing:`
😊 `:blush:`	😃 `:smiley:`	☺️ `:relaxed:`
😏 `:smirk:`	😍 `:heart_eyes:`	😘 `:kissing_heart:`
😚 `:kissing_closed_eyes:`	😳 `:flushed:`	😌 `:relieved:`
😆 `:satisfied:`	😁 `:grin:`	😉 `:wink:`
😜 `:stuck_out_tongue_winking_eye:`	😝 `:stuck_out_tongue_closed_eyes:`	😀 `:grinning:`
😗 `:kissing:`	😙 `:kissing_smiling_eyes:`	😛 `:stuck_out_tongue:`

	#!/usr/bin/env bash
	# Script to clone top repos on github based on language and invoke ShiftLeft Scan against the repos to find vulnerabilities
	# Use case 1: Scan the top repos on GitHub and write a state of opensource report to criticize opensource!
	# Use case 2: Scan the top repos on GitHub and sell your magical security product to guard organizations against opensource vulnerabilities!
	CURR_DIR=$(pwd)
	mkdir -p reports_dir
	mkdir -p work_dir && cd work_dir

	# Get the latest scan image
	docker pull shiftleft/scan

	// per https://docs.npmjs.com/misc/scripts, npm exposes a bunch of variables to
	// the environment prefixed with npm_config_, npm_package_ and npm_lifecycle_*.
	// Here's a list of all variables exposed in my setup.

	npm_config_access=
	npm_config_allow_same_version=
	npm_config_also=
	npm_config_always_auth=
	npm_config_argv='{"remain":[],"cooked":["run","foo"],"original":["run","foo"]}'
	npm_config_auth_type=legacy

	license: apache-2.0
	height: 600
	border: no