Tree: ecf5e2bd2c

Commit Graph

2 Commits (ecf5e2bd2cdb3112210ab513c33ae5af4f1a20ce)

Author	SHA1	Message	Date
James Rose	68faee2efd	Schedule data export tasks in sidekiq-cron (#952 An error occurred ) ... * Schedule data export tasks in sidekiq-cron - Split combined XML and CSV data jobs into seperate background jobs - Add sidekiq-cron to the project - Schedule new XML and CSV jobs to run every day at 5am - Adjust data export Rake tasks to use new job * Add specs for DataExport{Xml,Csv}Job * x * Run bundle install * Change review app export bucket name --------- Co-authored-by: Kat <katrina@kosiak.co.uk>	2 years ago
baarkerlounger	6f54c0c979	Switch to JSBundling with webpack (#392 An error occurred ) ... * Switch to JSBundling with webpack * Set babel target attempt 1 * Fix loose babel warning * Babel target attempt 2 * Babel target attempt 3 * Maybe we need to polyfill more than just promise... * Fix promise undefined in IE11 * Target oldest browsers possible * Set browserlist in package.json * Development mode browserlist and update readme * Mode flag * Does setting es5 web target help? * It doesn't * Not using ActiveStorage * Import all of corejs * Destructuring including in present-env already * Just import what we need * Add polyfill for fetch * Stimulus polyfills * Remove unused duplicates * We don't use channels * Single babel config * Stimulus working * Add additional polyfills for Stimulus and Turbo * Additional polyfill for Turbo * Make sure we also transpile our own stimulus controller code * Add plugin-transform-spread * Defaults are fine for most babel plugins * Plugin ordering * Specify which bits exactly we want to transpile * Transpiling turbo appears to break it * Devise logout via get so we don't rely on js * Override public path for IE11 * Need to make DOM event triggers explicit for IE11 * Update helper spec * Update helper spec * Bump dependencies	3 years ago