Testing front end code using rollup, tape-modern, and puppeteer.
These are just some notes for me to write down so that I have a good cheatsheet to set this up in the future.
Using rollup to build front end code is the way to go, it is small and provides tree shaking and the plugins are easy to manage. Using rollup to build a test bundle and using puppeteer to run the test bundle will create a chromium head browser and give you similar results as if you are running it in the browser.
| #!/bin/bash | |
| find . -name '*.php' | xargs -i php -l {} | grep -v 'No syntax errors' |
| sourceMapper = require 'source-map-support' | |
| Dot = require '../../../node_modules/grunt-mocha/node_modules/mocha/lib/reporters/dot.js' | |
| module.exports = Dot | |
| ## | |
| parseLine = (line) -> | |
| [_, file, row] = line.match /file:\/\/\/(.*):(\d*)/ | |
| frame = | |
| getFileName: -> file |
| #!/usr/bin/env python -O | |
| # | |
| # Copyright (c) 2013 Kyle Gorman | |
| # | |
| # Permission is hereby granted, free of charge, to any person obtaining a | |
| # copy of this software and associated documentation files (the | |
| # "Software"), to deal in the Software without restriction, including | |
| # without limitation the rights to use, copy, modify, merge, publish, | |
| # distribute, sublicense, and/or sell copies of the Software, and to | |
| # permit persons to whom the Software is furnished to do so, subject to |
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.