An emulator of user behavioural actions for SPAs. Could be used as a part of Remote Control functionality.
- Open https://artsiom.mezin.eu/preoccupyjs/demo.
- Click Activate remote control.
- Click Control to open a new tab, it's going to open a new tab.
- In the new tab click Connect. You will see a system dialog to choose the window to broadcast the screen media. Please, select the third tab with the title "Chrome Tab". From the options list select the tab with the title "PreoccupyJS. Test Application".
The main idea of the PreoccupyJS package is to emulate users actions within a remote-controlled SPA and to change the SPA's DOM accordingly.
Under the hood PreoccupyJS consists of the next main parts:
- Host - A controller for the host tab (machine), it's responsible for the collecting of Actions (user events) and transmitting it to the client tab using Transport.
- Client - A controller for the client tab (machine), it's responsible for the Actions interpreting and performing on the client page.
- Actions - A quantum of information which is collected from the Host side. It describes a single user action (like click, mousemove, scroll, etc...). Each action is transmitted to the Client tab (machine) by the Transport and performed over there by the Client.
- Transport - An abstract class. A Transport implementation allows Actions to be transmitted from the host tab to the client one.
PreoccupyJS doesn't provide any functionality to grab, broadcast, or present Screen Media streams. You have to take care about this part of fuctionality separetly.
Install from NPM
npm install --save-dev preoccupyjs
On the Host side:
- Import the Host and required Transport constructors
- Preapre a focusable DOM element, which is going to play a role of "touch screen" for the remote controller.
const hostEl = document; // fill free to style and modify this element as you wish, but don't delete it!hostEltabIndex = 0; // make it focusable
- Set up the transport
const transport = options assubject: Subject<object>; // an AnonymousSubject, e.g. WebSocketSubjectwrapFn?: object; // wraps a preoccupyJS message to make it fits for your Subject type;
- Set up and run the host
const host = transport hostEl;hoststart; // run the communication whenever your app is ready!
On the client side:
- Import the Client, DomController, and required Transport constructors
- Set up the transport
const transport = options assubject: Subject<object>; // an AnonymousSubject, e.g. WebSocketSubjectfilterFn?: boolean; // filter all messages in subject to avoid non-preoccupyjs related;
- Set up and run the client
const client = transport documentbody; // you can specify the controlled scope of the page by passing any other DOM elementclientstart; // run the communication whenever your app is ready!
- Preoccupyjs has a modular structure. You can reuse existing Actions or replace/extend it by your own.
- Preoccupyjs is totally transport agnostic. It's up to you how to transmit the actions between host and client browser tab.
You can import the generated bundle to use the whole library generated by this starter:
Additionally, you can import the transpiled modules (transports, actions) from
npm t: Run test suite
npm start: Run
npm run buildin watch mode
npm run test:watch: Run test suite in interactive watch mode
npm run test:prod: Run linting and generate coverage
npm run build: Generate bundles and typings, create docs
npm run lint: Lints code
npm run commit: Commit using conventional commit style (husky will tell you to use it if you haven't 😉)
On library development, one might want to set some peer dependencies, and thus remove those from the final bundle. You can see in Rollup docs how to do that.
Good news: the setup is here for you, you must only include the dependency name in
external property within
rollup.config.js. For example, if you want to exclude
lodash, just write there
Prerequisites: you need to create/login accounts and add your project to:
npm install --global --production windows-build-tools
Follow the console instructions to install semantic release and run it (answer NO to "Do you want a
.travis.yml file with semantic-release setup?").
Note: make sure you've setup
repository.url in your
npm install -g semantic-release-clisemantic-release-cli setup# IMPORTANT!! Answer NO to "Do you want a `.travis.yml` file with semantic-release setup?" question. It is already prepared for you :P
From now on, you'll need to use
npm run commit, which is a convenient way to create conventional commits.
Automatic releases are possible thanks to semantic release, which publishes your code automatically on github and npm, plus generates automatically a changelog. This setup is highly influenced by Kent C. Dodds course on egghead.io
There is already set a
precommit hook for formatting your code with Prettier 💅
By default, there are two disabled git hooks. They're set up when you run the
npm run semantic-release-prepare script. They make sure:
- You follow a conventional commit message
- Your build is not going to fail in Travis (or your CI server), since it's runned locally before
This makes more sense in combination with automatic releases
Map... is undefined?
TypeScript or Babel only provides down-emits on syntactical features (
async/await...), but not on functional features (
Promise...), . For that, you need Polyfills, such as
babel-polyfill (which extends
For a library,
core-js plays very nicely, since you can import just the polyfills you need:
Contributions of any kind are welcome!