JS packaging is complicated and testing it manually is irritating. Add a tool in `automerge-js/e2e` which stands up a local NPM registry and publishes the various packages to that registry for use in automated and manual tests. Update the test script in `scripts/ci/js_tests` to run the tests using this tool
		
			
				
	
	
		
			13 lines
		
	
	
	
		
			443 B
		
	
	
	
		
			Text
		
	
	
		
			Executable file
		
	
	
	
	
			
		
		
	
	
			13 lines
		
	
	
	
		
			443 B
		
	
	
	
		
			Text
		
	
	
		
			Executable file
		
	
	
	
	
| set -e
 | |
| 
 | |
| THIS_SCRIPT=$(dirname "$0");
 | |
| WASM_PROJECT=$THIS_SCRIPT/../../automerge-wasm;
 | |
| JS_PROJECT=$THIS_SCRIPT/../../automerge-js;
 | |
| E2E_PROJECT=$THIS_SCRIPT/../../automerge-js/e2e;
 | |
| 
 | |
| yarn --cwd $E2E_PROJECT install;
 | |
| # This will build the automerge-wasm project, publish it to a local NPM
 | |
| # repository, then run `yarn build` in the `automerge-js` directory with
 | |
| # the local registry
 | |
| yarn --cwd $E2E_PROJECT e2e buildjs;
 | |
| yarn --cwd $JS_PROJECT test
 |