Why Gemfury? Push, build, and install  RubyGems npm packages Python packages Maven artifacts PHP packages Go Modules Debian packages RPM packages NuGet packages

Repository URL to install this package:

Details    
Size: Mime:
dev:
	yarn storybook

# todo - to yarn link, we need to output somewherre else
# that means we need to update aliases since they go to dist
# otherwise make dev outputs ui-component-library storybook only code
# overwriting the build
clean:
	npx rimraf dist && mkdir -p dist

babel:
	NODE_ENV=development BABEL_ENV=development npx babel dist --out-dir dist || true

compile:
	npx tsc -p tsconfig.json || true

types:
	npx tsc --declaration --declarationDir dist/typings || true

JENKINS:
	yarn install

deploy:
	yarn run deploy

# $(MAKE) JENKINS &&
publish:
	$(MAKE) clean && $(MAKE) types && $(MAKE) compile && $(MAKE) babel && $(MAKE) cleanup

# copy & mv, but can copy with rename as per below
# cp -f package.build.json dist;
# mv dist/package.build.json dist/package.json;
cleanup:
	pwd;\
	mv ./dist/src/* ./dist && npx rimraf ./dist/src;\
	rm -rf ./dist/node_modules;\
	rm -rf ./dist/bootstrapper;\
	rm -rf ./dist/config;\
	rm -rf ./dist/stories;\
	rm -rf ./dist/typings/stories;\
	rm -rf ./dist/typings/node_modules;\
	pwd;\
	cp -f package.build.json dist/package.json;\
	pwd;\

# @todo rimraf dist/src & typings => it is exporting old files!!!
# @todo rimraf dist/node_modules & .git
# git commit --ammend "build";
automated:
	make publish;\
	cp -R package.json dist;\
	cd dist;\
	rm -f node_modules;\
	rm -f config;\
	git init;\
	git remote add origin https://bitbucket.org/skava-admin/ui-component-library.git;\
	git checkout -b branch_name_here;\
	git add -A
	git commit -m "build 0.4.0";\
	git push origin HEAD:branch_name_here;\

# @todo add prepush
lint:
	yarn tslint --project tsconfig.json --format stylish