Introduction Together with a colleague I started working on . Like a lot of projects this consists of a web api that does some stuff and a front-end. Partei To make things easy we decided to serve our front-end from the same server that serves our api and to keep them in the same git repository. We opted for ASP.NET Core in the back-end and in the front. React We set up the projects and configured Travis CI to run our tests and publish to Heroku. Initially we only had .NET tests and Travis ran them without a problem. But then we introduced Jest tests for the front-end. Travis CI has installed by default on the .NET environment so thing should go smooth. Node.js But things didn’t go smooth. Apparently the default version of Node.js is 4 and our project is written using Node.js 8. Time to figure out a solution for this. Solution I created a with a .NET Core test project and an npm project both with a simple test. repo _dotnetcore_node_travis - Running tests for dotnet and a specific version of node together in one Travis build_github.com bartw/dotnetcore_node_travis On Travis CI, Node Version Manager ( ) is available. In my .travis.yml file I used nvm to install Node.js 8 and use this version to run our tests. nvm Now both the .NET tests and the Node.js tests are running together. is how hackers start their afternoons. We’re a part of the family. We are now and happy to opportunities. Hacker Noon @AMI accepting submissions discuss advertising & sponsorship To learn more, , , or simply, read our about page like/message us on Facebook tweet/DM @HackerNoon. If you enjoyed this story, we recommend reading our and . Until next time, don’t take the realities of the world for granted! latest tech stories trending tech stories
