npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@fullstackcraftllc/codevideo-frontend

v1.1.7

Published

The frontend engine to create videos on codevideo.io

Downloads

15

Readme

codevideo-frontend

The frontend engine used to create videos on https://codevideo.io

This package is about as unstable as you can get. Consider it even below alpha status. It is brand new and under considerable development.

GitHub Pages Example

View a React example of codeToVideo in action on the example site.

Get Started

Install this package:

npm install --save @fullstackcraftllc/codevideo-frontend

This will also install the required dependency @fullstackcraftllc/codevideo-core

Given the following HTML / JSX markup:

<canvas id="canvas" />

Import and call codeToVideo:

import { codeToVideo, MimicTypos } from "@fullstackcraftllc/codevideo-frontend";

// define video parameters
const fps = 60;
const mimeType = "video/webm";
const codec = "codecs=vp9";

// get canvas and setup media recorder
const canvas = document.getElementById("canvas") as HTMLCanvasElement;

const { videoUrl, error } = await codeToVideo(
  canvas,
  fps,
  mimeType,
  codec,
  1920,
  1080,
  "print('hello world!')",
  "python",
  ["red", "blue"],
  MimicTypos.NEVER
);
if (error) {
  // handle error
  console.error(error);
}
// No error, so we can do something with videoUrl.

// In this example, create a video element, set its source, and append it to a container

// Create the video element
const video = document.createElement("video");

// Set the video's src attribute to the URL of a video file
video.src = videoUrl;

// Set other useful attributes
video.id = "video";
video.height = 960;
video.width = 540;
video.controls = true;
video.autoplay = true;

// Append the video element to the container div
const container = document.getElementById("container");
if (container) {
  container.appendChild(video);
}

The canvas doesn't even have to be visible on the page. It can be off-screen or in a hidden div.

Happy video making!

For Developers

  1. Clone this repository:
git clone https://github.com/codevideo/codevideo-frontend.git
  1. Install dependencies:
npm install
  1. Run the tests:
npm test
  1. Optionally, run the example site locally:
cd example
npm install
npm start

Deploys

Deploys are run with Circle CI. Merging to the main branch will trigger first tests and code coverage, then packaging. If this all works, this triggers a merge from main to release, where it is finally published to the release branch. You can see all these CI/CD processes in .circleci/config.yml directory.

Publishing

This package can only be published when logged in as the @fullstackcraftllc user (really a note for Chris to himself more than anything).