APKBUILD examples:JavaScript - Revision history

WhyNotHugo: `cd $builddir` is no longer necessasry

2025-08-18T18:07:55Z

`cd $builddir` is no longer necessasry

← Older revision		Revision as of 18:07, 18 August 2025
Line 25:		Line 25:

	build() {		build() {
	~~cd "$builddir"~~
	npm install		npm install
	}		}
Line 36:		Line 35:

	package() {		package() {
	~~cd "$builddir"~~
	install -d "$pkgdir"/usr/share/doc/$pkgname "$pkgdir"/usr/lib/node_modules/$pkgname		install -d "$pkgdir"/usr/share/doc/$pkgname "$pkgdir"/usr/lib/node_modules/$pkgname
	cp -a bin lib node_modules package*.json "$pkgdir"/usr/lib/node_modules/$pkgname		cp -a bin lib node_modules package*.json "$pkgdir"/usr/lib/node_modules/$pkgname
Line 45:		Line 43:

	check() {		check() {
	~~cd "$builddir"~~
	npm test		npm test
	}		}

2018-03-03T04:16:47Z

Package: remove unnecessary line

← Older revision		Revision as of 04:16, 3 March 2018
Line 39:		Line 39:
	install -d "$pkgdir"/usr/share/doc/$pkgname "$pkgdir"/usr/lib/node_modules/$pkgname		install -d "$pkgdir"/usr/share/doc/$pkgname "$pkgdir"/usr/lib/node_modules/$pkgname
	cp -a bin lib node_modules package*.json "$pkgdir"/usr/lib/node_modules/$pkgname		cp -a bin lib node_modules package*.json "$pkgdir"/usr/lib/node_modules/$pkgname
	~~cd "$pkgdir"/usr/lib/node_modules/$pkgname~~
	ln -s /usr/lib/node_modules/$pkgname/bin/$pkgname "$pkgdir"/usr/bin		ln -s /usr/lib/node_modules/$pkgname/bin/$pkgname "$pkgdir"/usr/bin
	}		}

2018-03-03T03:39:41Z

Package: symlink only the main or major programs of interest

← Older revision		Revision as of 03:39, 3 March 2018
Line 33:		Line 33:
	This is a simple example without documentation. You need to package the bin folder, the package*.json file, and the lib folder. There may be other files that need to be packaged. All apps should be placed in the "$pkgdir"/usr/lib/node_modules/$pkgname to make them visible for other nodejs programs or to keep track of the npm dependencies for CVE check for future tool.		This is a simple example without documentation. You need to package the bin folder, the package*.json file, and the lib folder. There may be other files that need to be packaged. All apps should be placed in the "$pkgdir"/usr/lib/node_modules/$pkgname to make them visible for other nodejs programs or to keep track of the npm dependencies for CVE check for future tool.

	You also want to place symlinks for some programs but not all because there is some overlap between npm apps for compatibility reasons and the native apps.		You also want to place symlinks for some programs but not all because there is some overlap between npm apps for compatibility reasons and the native apps. Only symlink the main or major programs not the dependencies.

	package() {		package() {

2018-03-03T03:36:15Z

Package: just provide the basic files and folders

← Older revision		Revision as of 03:36, 3 March 2018
Line 38:		Line 38:
	cd "$builddir"		cd "$builddir"
	install -d "$pkgdir"/usr/share/doc/$pkgname "$pkgdir"/usr/lib/node_modules/$pkgname		install -d "$pkgdir"/usr/share/doc/$pkgname "$pkgdir"/usr/lib/node_modules/$pkgname
	cp -a bin lib node_modules ~~scripts~~ package*.json "$pkgdir"/usr/lib/node_modules/$pkgname		cp -a bin lib node_modules package*.json "$pkgdir"/usr/lib/node_modules/$pkgname
	cd "$pkgdir"/usr/lib/node_modules/$pkgname		cd "$pkgdir"/usr/lib/node_modules/$pkgname
	ln -s /usr/lib/node_modules/$pkgname/bin/$pkgname "$pkgdir"/usr/bin		ln -s /usr/lib/node_modules/$pkgname/bin/$pkgname "$pkgdir"/usr/bin

2018-03-03T03:30:42Z

Licensing: fix markup

← Older revision		Revision as of 03:30, 3 March 2018
Line 52:		Line 52:
	== Licensing ==		== Licensing ==

	Since you are packaging the dependencies and the app under one package, you should list all the licenses for those dependencies in the license field. Use <code>grep<c/~~ode~~> and <code>find</code> to find them.		Since you are packaging the dependencies and the app under one package, you should list all the licenses for those dependencies in the license field. Use <code>grep</code> and <code>find</code> to find them.

	== Security updates ==		== Security updates ==

2018-03-03T03:28:49Z

Build: must have package.json present

← Older revision		Revision as of 03:28, 3 March 2018
Line 22:		Line 22:
	== Build ==		== Build ==

	In this step we tell <code>npm</code> to get the dependencies and build the binary dependencies if any. These dependencies will be placed in a folder called node_modules in the same directory as the package.json. You may need to do this repetitively at the root level and in the app folder if any.		In this step we tell <code>npm</code> to get the dependencies and build the binary dependencies if any. These dependencies will be placed in a folder called node_modules in the same directory as the package.json. You may need to do this repetitively at the root level and in the app folder if any, or wherever you see a package.json file without a node_modules.

	build() {		build() {

2018-03-03T03:25:31Z

Build: repetitive calls may be required

← Older revision		Revision as of 03:25, 3 March 2018
Line 22:		Line 22:
	== Build ==		== Build ==

	In this step we tell <code>npm</code> to get the dependencies and build the binary dependencies if any. These dependencies will be placed in a folder called node_modules in the same directory as the package.json.		In this step we tell <code>npm</code> to get the dependencies and build the binary dependencies if any. These dependencies will be placed in a folder called node_modules in the same directory as the package.json. You may need to do this repetitively at the root level and in the app folder if any.

	build() {		build() {

2018-03-03T03:22:36Z

clarify

← Older revision		Revision as of 03:22, 3 March 2018
Line 4:		Line 4:
	Because there are literally hundreds of dependencies for a Node.js application, it makes more sense to just keep them all internal dependencies except those that require special patching. We are going to just cover the trivial packages easy packages for now.		Because there are literally hundreds of dependencies for a Node.js application, it makes more sense to just keep them all internal dependencies except those that require special patching. We are going to just cover the trivial packages easy packages for now.

	Again, only package applications not Node.js libraries, but only if the Node.js requires patching on musl.		Again, only package applications not Node.js libraries, but only if the Node.js package requires patching on musl.

	== Requirements ==		== Requirements ==

2018-03-03T03:21:16Z

only package applications

← Older revision		Revision as of 03:21, 3 March 2018
Line 3:		Line 3:

	Because there are literally hundreds of dependencies for a Node.js application, it makes more sense to just keep them all internal dependencies except those that require special patching. We are going to just cover the trivial packages easy packages for now.		Because there are literally hundreds of dependencies for a Node.js application, it makes more sense to just keep them all internal dependencies except those that require special patching. We are going to just cover the trivial packages easy packages for now.

			Again, only package applications not Node.js libraries, but only if the Node.js requires patching on musl.

	== Requirements ==		== Requirements ==

2018-03-03T03:18:44Z

Add category

← Older revision		Revision as of 03:18, 3 March 2018
Line 55:		Line 55:

	In an event of a CVE notice and a update to fix that CVE for a <code>npm</code> dependency, you need to rebuild the package(s) and increment the pkgrel.		In an event of a CVE notice and a update to fix that CVE for a <code>npm</code> dependency, you need to rebuild the package(s) and increment the pkgrel.

			[[Category:Development]]