cronofy-elements 1.48.2 → 1.49.2

package/package.json

@@ -1,8 +1,8 @@
 {
     "name": "cronofy-elements",
-    "version": "1.48.2",
+    "version": "1.49.2",
     "description": "Fast track scheduling with Cronofy's embeddable UI Elements",
-    "main": "build/npm/CronofyElements.js",
+    "main": "dist/CronofyElements.js",
     "scripts": {
         "test": "jest",
         "build": "webpack --mode=production",
@@ -15,12 +15,15 @@
         "dev_analyse": "webpack --mode=development --watch --analyze",
         "dev_compat": "webpack --config compat.config.js --mode=development --watch",
         "serve": "npm run build_server && node build/server.js",
-        "copy": "node -e \"if (!require('fs').existsSync('build/npm')){ require('fs').mkdirSync('build/npm') }; require('fs').copyFileSync('build/CronofyElements.v$npm_package_version.js','build/npm/CronofyElements.js')\"",
+        "copy_for_s3_upload": "node -e \"require('fs').copyFileSync('dist/CronofyElements.js', 'dist-s3/CronofyElements.v$npm_package_version.js')\"",
         "use:npmReadme": "mv 'README.md' 'git.README.md' && mv 'npm.README.md' 'README.md'",
         "use:gitReadme": "mv 'README.md' 'npm.README.md' && mv 'git.README.md' 'README.md'",
-        "prepublishOnly": "npm run use:npmReadme && npm run build && npm run copy",
-        "postpublish": "npm run use:gitReadme"
+        "prepack": "npm run use:npmReadme",
+        "postpack": "npm run use:gitReadme"
     },
+    "files": [
+        "/dist/**/*"
+    ],
     "jest": {
         "verbose": true,
         "collectCoverage": true,
@@ -81,8 +84,7 @@
         "moment": "^2.29",
         "moment-timezone": "^0.5",
         "moment-timezone-data-webpack-plugin": "^1.5",
-        "node-fetch": "^2.3",
-        "node-sass": "^6.0",
+        "node-fetch": "^2.6.7",
         "path": "^0.12",
         "polished": "^2.3",
         "postcss-loader": "^5.3",
@@ -94,6 +96,7 @@
         "react-emotion": "^9.2",
         "react-select": "^2.4",
         "react-transition-group": "^4.4",
+        "sass": "^1.49.0",
         "sass-loader": "^12.1",
         "style-loader": "^3.0",
         "terser-webpack-plugin": "^5.1",

package/.babelrc

@@ -1,20 +0,0 @@
-{
-    "presets": [
-        "@babel/preset-react",
-        ["@babel/preset-env", {
-            "useBuiltIns": "entry",
-            "corejs": "3.0.0",
-            "targets": { "ie": "11" } 
-        }],
-        [
-            "@emotion/babel-preset-css-prop",
-            {
-                "sourceMap": true
-            }
-        ],
-    ],
-    "plugins": [
-        "@babel/plugin-proposal-class-properties",
-        "@babel/plugin-proposal-object-rest-spread"
-    ]
-}

package/.eslintrc.yaml

@@ -1,43 +0,0 @@
----
-parser: "babel-eslint"
-
-extends:
-    - "eslint:recommended"
-    - "plugin:jsx-a11y/recommended"
-
-plugins:
-    - import
-    - unused-imports
-    - jsx-a11y
-    - react
-    - prettier
-
-parserOptions:
-    ecmaVersion: 6
-    sourceType: "module"
-    ecmaFeatures:
-        jsx: true
-
-env:
-    browser: true
-    node: true
-    es6: true
-    jest: true
-
-rules:
-    react/jsx-uses-react: "error"
-    react/jsx-uses-vars: "error"
-    import/imports-first: "error"
-    import/newline-after-import: "error"
-    import/no-dynamic-require: "off"
-    import/no-extraneous-dependencies: "error"
-    import/no-named-as-default: "off"
-    import/no-unresolved: "error"
-    import/no-webpack-loader-syntax: "error"
-    import/prefer-default-export: "off"
-    prettier/prettier: "error"
-    unused-imports/no-unused-imports: "warn"
-    no-unused-vars: "off"
-    no-case-declarations: "off"
-    no-prototype-builtins: "off"
-    no-extra-boolean-cast: "off"

package/.prettierignore

@@ -1,4 +0,0 @@
-# Ignore artifacts:
-build
-coverage
-demo

package/.prettierrc

@@ -1,7 +0,0 @@
-{
-    "arrowParens": "avoid",
-    "tabWidth": 4,
-    "useTabs": false,
-    "trailingComma": "es5",
-    "printWidth": 100
-}

package/Makefile

@@ -1,92 +0,0 @@
-.PHONY: default
-default: install dev
-
-.PHONY: install
-install:
-	yarn install
-
-.PHONY: init
-init: install
-	npm run build_dev
-
-.PHONY: clean
-clean:
-	rm -rf build/*
-
-.PHONY: env_check
-env_check:
-ifeq ("$(wildcard ./src/js/env.js)","")
-	echo "./src/js/env.js does not exist, see ./src/js/env.example.js for a reference"
-	exit 1
-endif
-
-.PHONY: dev
-dev: env_check
-	npm run dev &
-	npm run serve
-
-.PHONY: dev_compat
-dev_compat: env_check
-	npm run dev_compat &
-	npm run serve
-
-.PHONY: build
-build: install
-	npm run build
-
-.PHONY: rebuild
-rebuild: clean build
-
-.PHONY: ci
-ci: clean
-	yarn install --frozen-lockfile
-	npm run test
-
-.PHONY: test
-test: install
-	npm run test
-
-.PHONY: lint
-lint:
-	npx eslint src
-
-.PHONY: lint-fix
-lint-fix:
-	node_modules/eslint/bin/eslint.js --fix src
-
-.PHONY: publish_npm
-publish_npm:
-	npm config set '//registry.npmjs.org/:_authToken' "$${NPM_TOKEN:?}"
-	npm run test
-	npm publish
-
-.PHONY: publish
-publish: rebuild publish_npm
-	aws s3 cp ./build s3://cronofy-management-ui-elements/js/ --recursive --acl bucket-owner-full-control
-
-.PHONY: build_dev
-build_dev:
-	npm run build_dev
-
-.PHONY: bump_version
-bump_patch:
-	yarn version --patch --no-git-tag-version
-	npm run build
-
-.PHONY: bump_minor
-bump_minor:
-	yarn version --minor --no-git-tag-version
-	npm run build
-
-.PHONY: bump_major
-bump_major: build
-	yarn version --major --no-git-tag-version
-	npm run build
-
-.PHONY: i18n-export
-i18n-export:
-	script/i18n-export
-
-.PHONY: i18n-import
-i18n-import:
-	script/i18n-import

package/brainstorm.md

@@ -1,76 +0,0 @@
-# Components: brainstorm
-
-There are three components to be built (for now - there is scope for more in the future):
-
-* Availability Rules
-* Availability Viewer
-* Calendar View
-
-## Rules (do not forget these!)
-
-* Translate all the ~things~ strings!
-* Use a linter (Prettier for JS will be fine)
-* Use an `.editorconfig` file
-* Minimum target of 80% test coverage
-
-## Common issues
-
-There are certain aspects that are common to all components, and these will need to be defined (or at least planned for) before work is begun on the components themselves.
-
-* Authentication
-    - how do we generate a secure token for locked-down API access?
-    - can we cache the tokens?
-    - how do we handle authentication for multiple components on the same page?
-* Embedding
-    - what is the best way to get our code inside a client's app? Using an `iFrame` would probably be simplest, but is inelegant and requires exact positioning (and width/height) of the frame to avoid layout bugs. Can we use a "web component"?
-    - what level of user-setup do we expect? The simpler the better, ideally: "here's three lines of code. Throw those into your application and the component will work".
-    - [Web Components](https://www.webcomponents.org/introduction) and [Shadow DOM](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM) in theory allow a "modern" equivalent to sandboxed iFrames. Sadly too modern for most browsers, so would require a polyfill for *most* users. [Polyfill](https://github.com/WebComponents/webcomponentsjs) is \~94kB 
-* Distribution: a.k.a. how do we publish the components?
-    - Packages on NPM (or lang. equivalent)?
-    - CDN version
-
----
-
-## Availability Rules
-
-* Set timezone
-* Set target calendar
-* Set rules by time blocks (e.g. "Tues 0900 - 1300")
-* Add multiple rules (in list form, *a la* a classic to-do-list app)
-
----
-
-## Availability Viewer
-
-Divided into "core" and "enhanced" features. Core has basic functionality: it just shows the calendar grid. The enhanced version includes features like the user-selector, and event-duration-selector.
-
-### Core
-
-* Takes inputs:
-    - member IDs (the users who's calendars we have access to)
-    - auth token
-* Calendar (table-view style)
-* Navigate between dates?
-
-### Enhanced
-
-* set duration of event (e.g. 30mins/60mins)
-* Select users (a.k.a. users' calendars) to pull availability from
-* Range-style slider to constrain grid-view times (e.g. only show slots between 9am and 1pm)
-
-### To be resolved
-
-* What happens when an available slot is clicked? 
-
-1. How versatile does the functionality need to be? i.e. just for "interviews"?
-2. "send booking form to candidate" - similar to 1., how flexible does this need to be?
-3. Do the "candidate" and "role" sections need to be part of the component too? (Or separate components, maybe?)
-4. Responsiveness? Assuming there will be a "minimum viable width"...
-
----
-
-## Calendar View
-
-* compact view (e.g. for a sidebar widget)
-* Show events schedules for 1 day, for one user's calendar
-* navigate between days?