@internetarchive/bookreader 5.0.0-18

package/.eslintrc.js

@@ -0,0 +1,58 @@
+module.exports = {
+  "parser": "babel-eslint",
+  "env": {
+    "browser": true,
+    "jquery": true,
+    "es6": true,
+    "node": true,
+    "jest": true
+  },
+  "plugins": [
+    "testcafe",
+    "no-jquery"
+  ],
+  "extends": [
+    "eslint:recommended",
+    "plugin:testcafe/recommended",
+    "plugin:no-jquery/deprecated"
+  ],
+  "globals": {
+    // Browser API
+    "MediaMetadata": "readonly"
+  },
+  "parserOptions": {
+    "ecmaVersion": 2020,
+    "ecmaFeatures": { "legacyDecorators": true },
+    "sourceType": "module"
+  },
+  "rules": {
+    "comma-dangle": ["error", "only-multiline"],
+    "semi": ["error", "always"],
+    "space-before-blocks": ["error"],
+    "keyword-spacing": [2, {"before": true, "after": true}],
+    "indent": ["error", 2, {
+      // This for some reason causing errors after switch to parser: babel-eslint.
+      // See https://github.com/babel/babel-eslint/issues/681
+      "ignoredNodes": ["TemplateLiteral"]
+    }],
+    "no-console": "off", // Used too often behind `debug` options; not dealing with this now
+    "no-empty": ["error", { "allowEmptyCatch": true }],
+    "no-trailing-spaces": ["error"],
+    "no-unused-vars": ["error", { "vars": "all", "args": "none", "ignoreRestSiblings": false }], // set args:none; this is generally more annoying than useful
+    "no-var": ["error"],
+    "prefer-const": ["error"],
+    "space-infix-ops": ["error", { "int32Hint": false }],
+    "eol-last": ["error", "always"]
+  },
+  "overrides": [
+    { // TODO; these should be cleaned up as well
+      "files": [
+        "src/BookReader.js",
+        "src/dragscrollable-br.js"
+      ],
+      "rules": {
+        "no-var": ["off"],
+      }
+    },
+  ],
+};

package/.gitattributes

@@ -0,0 +1,2 @@
+# Build files
+BookReader/**/* binary

package/.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,32 @@
+---
+name: Bug
+about: A general problem with website functionality
+title: ''
+labels: Bug
+assignees: ''
+
+---
+
+**Description**
+
+> What problem are we solving? What does the experience look like today? What are the symptoms? How can one reproduce the problem?
+
+**Evidence / Screenshot (if possible)**
+
+> Include evidence of the problem or provide a screenshot.
+
+**Expectation**
+
+> What should be happening? What will it look like / how will it behave when fixed?
+
+**Context**
+
+> What operating system? What browser type and version?
+
+**Proposal & Constraints**
+
+> What is the proposed solution / implementation? Is there a precedent of this approach succeeding elsewhere?
+
+**Stakeholders**
+
+> @-tag any stakeholders of this bug

package/.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,30 @@
+---
+name: Feature Request
+about: A request for an entirely new feature
+title: ''
+labels: Feature Request
+assignees: ''
+
+---
+
+**Context**
+
+> Is your feature request related to a problem? What is the motivation for implementing this feature?
+
+**Proposal & Constraints**
+
+> What is the proposed solution / implementation? Is there a precedent for this approach succeeding elsewhere?
+
+> Which suggestions or requirements should be considered for how this feature needs to appear or be implemented?
+
+**Additional Resources**
+
+> Add any other screenshots or assets related to the feature request.
+
+**Success Metrics**
+
+> How will you know if this change is successful? What specific metrics are relevant and how do you expect them to change?
+
+**Stakeholders**
+
+> @-tag stakeholders of this feature

package/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,15 @@
+**Description**
+
+> What does this PR achieve? Is it a feature/bugfix/refactor? Does it close an Issue? If so, use `Closes #<issue number>`.
+
+**Technical**
+
+> What should be noted about the implementation?
+
+**Testing**
+
+> What steps should the reviewer take to verify this PR resolves the issue?
+
+**Screenshots/Videos**
+
+> Add a screenshot or video/GIF if the fix can be seen visually. This is helpful for reviewers to get context for the fix.

package/.github/dependabot.yml

@@ -0,0 +1,8 @@
+version: 2
+updates:
+- package-ecosystem: npm
+  directory: "/"
+  schedule:
+    interval: monthly
+    time: "13:00"
+  open-pull-requests-limit: 10

package/.github/workflows/node.js.yml

@@ -0,0 +1,37 @@
+# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
+# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
+
+name: Node.js CI
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - uses: actions/setup-node@v1
+      with:
+        node-version: 14.x
+    - uses: actions/cache@v2
+      with:
+        # Caching node_modules isn't recommended because it can break across
+        # Node versions and won't work with npm ci (See https://github.com/actions/cache/blob/main/examples.md#node---npm )
+        # But we pin the node version, and we don't update it that often anyways. And 
+        # we don't use `npm ci` specifically to try to get faster CI flows. So caching
+        # `node_modules` directly.
+        path: 'node_modules'
+        key: ${{ runner.os }}-node-${{ hashFiles('package*.json') }}
+    - run: npm install
+    - run: npm run build
+    - run: npm run lint
+    - run: npm run test
+    - run: npm run codecov
+    # Travis machines usually have 2 cores (see https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system )
+    # Quarantine mode (sigh) to catch unstable tests (see https://devexpress.github.io/testcafe/documentation/guides/basic-guides/run-tests.html#quarantine-mode )
+    - run: BASE_URL=http://127.0.0.1:8000/BookReaderDemo/ npx testcafe --concurrency 2 --quarantine-mode

package/.github/workflows/npm-publish.yml

@@ -0,0 +1,47 @@
+# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
+# For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
+
+name: Node.js Package
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 14
+      - run: npm ci
+      - run: npm test
+
+  publish-npm:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 14
+          registry-url: https://registry.npmjs.org/
+      - run: npm ci
+      - run: npm publish --tag next
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}
+
+  publish-gpr:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: 14
+          registry-url: https://npm.pkg.github.com/
+      - run: npm ci
+      - run: npm publish --tag next
+        env:
+          NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}

package/.testcaferc.json

@@ -0,0 +1,5 @@
+{
+  "appCommand": "npm run serve",
+  "browsers": ["chrome:headless", "firefox:headless"],
+  "src": ["tests/e2e/**/*test.js"]
+}