scorm-again 1.6.1 → 1.7.0

package/.circleci/config.yml

@@ -19,11 +19,6 @@ jobs:
     steps:
       - checkout
 
-      # Update npm
-      - run:
-          name: update-npm
-          command: 'sudo npm install -g npm@latest'
-
       # Download and cache dependencies
       - restore_cache:
           keys:
@@ -31,7 +26,7 @@ jobs:
             # fallback to using the latest cache if no exact match is found
             - v1-dependencies-
 
-      - run: npm install
+      - run: yarn install
 
       - save_cache:
           paths:
@@ -42,7 +37,7 @@ jobs:
 
       # Run mocha
       - run:
-          name: npm test
+          name: yarn test
           command: ./node_modules/.bin/nyc ./node_modules/.bin/mocha --require @babel/register --recursive --timeout=10000 --exit --reporter mocha-junit-reporter --reporter-options mochaFile=test-results/mocha/results.xml
           when: always
 
@@ -78,7 +73,7 @@ jobs:
 
       # run babel compile
       - run: git config user.email "jputney@noverant.com" && git config user.name "Jonathan Putney"
-      - run: ./node_modules/.bin/grunt
+      - run: ./node_modules/.bin/webpack --bail --config webpack.js
       - run: git add --all dist/
 
       # run jsdoc
@@ -101,4 +96,4 @@ jobs:
 
       - store_artifacts: # upload test coverage as artifact
           path: ./coverage/lcov.info
-          prefix: tests
+          prefix: tests

package/README.md

@@ -59,7 +59,11 @@ The APIs include several settings to customize the functionality of each API:
 | `mastery_override` | false | true/false | (SCORM 1.2) Used to override a module's `cmi.core.lesson_status` so that a pass/fail is determined based on a mastery score and the user's raw score, rather than using whatever status is provided by the module. An example of this would be if a module is published using a `Complete/Incomplete` final status, but the LMS always wants to receive a `Passed/Failed` for quizzes, then we can use this setting to override the given final status. |
 | `selfReportSessionTime` | false | true/false | Should the API override the default `session_time` reported by the module? Useful when modules don't properly report time. |
 | `alwaysSendTotalTime` | false | true/false | Should the API always send `total_time` when committing to the LMS |
+| `xhrWithCredentials` | false | true/false | Sets the withCredentials flag on the request to the LMS |
+| `xhrHeaders` | {} | Object | This allows setting of additional headers on the request to the LMS where the key should be the header name and the value is the value of the header you want to send |
 | `responseHandler` | function |  | A function to properly tranform the response from the LMS to the correct format. The APIs expect the result from the LMS to be in the following format (errorCode is optional): `{ "result": true, "errorCode": 0 }` |
+| `requestHandler` | function |  | A function to transform the commit object before sending it to `lmsCommitUrl`. By default it's the identity function (no transformation). |
+| `onLogMessage` | function |  | A function to be called whenever a message is logged. Defaults to console.{error,warn,info,debug,log} |
 
 ## Initial Values
 
@@ -266,8 +270,8 @@ I welcome any and all feedback and contributions to this project! I'm sure it wo
 #### Setup and Development
 You will need `node` installed on your local machine, and you'll have to run `npm install` in the repo directory before starting development. 
 
-To run a build, you need to just run the `grunt` command in the root of the project.
+To run a build, you need to just run the `yarn run compile` command in the root of the project.
 
-Similarly, to run the tests, you just run the `grunt test` or `npm test` command.
+Similarly, to run the tests, you just run the `yarn test` command.
 
 Before submitting pull requests, please also run `eslint ./src --fix` against your code first, otherwise your pull request build could fail.