upstreamremote pointing back to the TypeORM repository that you forked in the first place.
ormconfig.jsonfile, run the following command:
build/packagedirectory. You can link (or simply copy/paste) this directory into your project and test TypeORM there (but make sure to keep all node_modules required by TypeORM).
build/typeorm-x.x.x.tgz). You can copy this tar into your project and run
npm install ./typeorm-x.x.x.tgzto bundle your build of TypeORM in your project.
<num>is the corresponding github issue. For example, if you were creating a PR to fix github issue #363, you'd create
./entity/<entity-name>.tsrelative to your
issue-<num>.tsfile, they will automatically be loaded.
ormconfig.jsonand replacing parameters with your own.
.onlymocha commands (describe, it). Example:
Hint: you can use the
--grepflag to pass a Regex to
gulp-mocha. Only the tests have have
itstatements that match the Regex will be run. For example:npm test -- --grep="github issues > #363"This is useful when trying to get a specific test or subset of tests to pass.
npm testscript works by deleting built TypeScript code, rebuilding the codebase, and then running tests. This can take a long time.
npm run compile -- --watchto make a fresh build and instruct TypeScript to watch for changes and only compile what code you've changed.
npm run test-fast(instead of
test), to trigger a test without causing a full recompile, which allows you to edit and check your changes much faster.
docker-compose upin the root of the project. Once all images are fetched and run you can run tests.