From 33bed47daca3f08c396215415e6ece005970734a Mon Sep 17 00:00:00 2001 From: Richard Westenra Date: Sat, 6 Apr 2019 11:07:05 +0300 Subject: [PATCH 1/2] Remove calls to missing modules from gruntfile When running the app, Grunt throws the following warnings: >> Local Npm module "grunt-contrib-clean" not found. Is it installed? >> Local Npm module "grunt-contrib-nodeunit" not found. Is it installed? These modules don't appear to do anything except throw a warning so they can probably just be removed. --- gruntfile.js | 3 --- 1 file changed, 3 deletions(-) diff --git a/gruntfile.js b/gruntfile.js index edebddd..7e35753 100644 --- a/gruntfile.js +++ b/gruntfile.js @@ -162,9 +162,6 @@ module.exports = grunt => { }); - grunt.loadNpmTasks('grunt-contrib-clean'); - grunt.loadNpmTasks('grunt-contrib-nodeunit'); - // Default task grunt.registerTask( 'default', [ 'css', 'js' ] ); From 1bacb27072ecd5b057ee68f29df6cad3ee5f76ce Mon Sep 17 00:00:00 2001 From: Jason Cooke Date: Fri, 5 Jul 2019 22:00:10 +1200 Subject: [PATCH 2/2] docs: fix typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 33956e9..e0e14f1 100644 --- a/README.md +++ b/README.md @@ -1237,7 +1237,7 @@ Then: Plugins should register themselves with reveal.js by calling `Reveal.registerPlugin( 'myPluginID', MyPlugin )`. Registered plugin instances can optionally expose an "init" function that reveal.js will call to initialize them. -When reveal.js is booted up via `Reveal.initialize()`, it will go through all registered plugins and invoke their "init" methods. If the "init" method returns a Promise, reveal.js will wait for that promise to be fullfilled before finshing the startup sequence and firing the [ready](#ready-event) event. Here's an example of a plugin that does some asynchronous work before reveal.js can proceed: +When reveal.js is booted up via `Reveal.initialize()`, it will go through all registered plugins and invoke their "init" methods. If the "init" method returns a Promise, reveal.js will wait for that promise to be fulfilled before finshing the startup sequence and firing the [ready](#ready-event) event. Here's an example of a plugin that does some asynchronous work before reveal.js can proceed: ```javascript let MyPlugin = {