The code in this file will register the cors middleware which will permit requests made from websites with a different origin.
Now that you have installed ffmpeg, you’ll set up a web server that responds to requests using Express.įirst, open a new file called server.mjs with nano or your editor of choice:
npm install -save express cors multer p-queue. The -save flag indicates that you wish to save those as dependencies in the package.json file. The -y parameter indicates that you’re happy with the default settings for the project.įinally, use npm install to install the packages required to build the API. Use npm init to create a new package.json file. Start by opening the terminal and creating a new directory for the project: In this step, you will create a project directory, initialize Node.js and install ffmpeg, and set up a basic Express server. Step 1 - Setting Up the Project and Creating a Basic Express Server This tutorial was verified with Node v16.11.0, npm v7.15.1, express v4.17.1, and ffmpeg.wasm v0.10.1. A video to download to test your implementation. You can take a look at the tutorial How To Add JavaScript to HTML to review placing JavaScript in HTML. Experience with building websites with HTML and JavaScript. See How To Get Started with Node.js and Express. Familiarity with building APIs with Express in Node.js. Follow How to Install Node.js and Create a Local Development Environment. A local development environment for Node.js. To complete this tutorial, you will need: You’ll also handle requests made to your API that cannot be processed in parallel. When you’re finished, you will have a good grasp on handling binary data in Express and processing them with ffmpeg.wasm. You can use the same techniques to add other features supported by FFmpeg to your API. You’ll build an endpoint that extracts a thumbnail from a video as an example. 
In this guide, you will build a media API in Node.js with Express and ffmpeg.wasm - a WebAssembly port of the popular media processing tool. Particularly at a smaller scale, it makes sense to add media processing capability directly to your Node.js API. However, the extra cost and added complexity may be hard to justify when all you need is to extract a thumbnail from a video or check that user-generated content is in the correct format. Using dedicated, cloud-based solutions may help when you’re dealing with massive scale or performing expensive operations, such as video transcoding. Handling media assets is becoming a common requirement of modern back-end services.
The author selected the Electronic Frontier Foundation to receive a donation as part of the Write for DOnations program.
0 kommentar(er)
