Jay McDoniel jmcdo29

I've always had trouble using the given node -r tsconfig-paths/register path/to/main function from the command line, my paths never import correctly and I always seem to have an error when running after a build. After doing a bunch of digging around through packages and StackOverflow Q&A's I finally found a way to use tsconfig-paths programatically.

The tsconfig-bootstrap.js file makes use of tsconfig-pathsto register the paths from the compiler, and more than likely does exactly what tsconfig-paths/register is supposed to do. After requiring your tsconfig file you can access your baseUrl and paths via the JSON scheme of the config file to 100% programatically set your path imports to be correct, so that is anything changes in your config file this function doesn't need any chagning!

After you have the function set up, jsut add the following segment to your npm start command (whatever you have it called) and watch as your server fires up seamlessly:

# normal start without bootstrap
node

I've run into trouble in the past with testing observables, so I figured I would make myself a gist to help myself remember, and to help others who find it.

Observables are rather tricky to test in general as they are made to be asynchronous and act like a stream, and up until recently it was acceptable to pass a next, error, and complete callback function, but now that method is bieng deprecated in favor of Observers. Fear not! An Observer is just like the three callbacks rolled into a signle object, plus other fields you would like to add :).

Say that we have the following Observable

const numbersArray = from([1,2,3,4,5]);