Welcome back to this series, all about uploading files to the web. If you miss , I’d recommend you check it out because it’s all about uploading files via . the first post HTML . Upload files with HTML . Upload files with JavaScript Receiving file uploads with Node.js (Nuxt.js). Optimizing storage costs with Object Storage. Optimizing delivery with a CDN. Securing file uploads with malware scans. In this post, we’ll do the same thing using . JavaScript https://www.youtube.com/watch?v=Zyjgc2bySZo&embedable=true We left the project off with the form that looks like this. <form action="/api" method="post" enctype="multipart/form-data"> <label for="file">File</label> <input id="file" name="file" type="file" /> <button>Upload</button> </form> In the previous post, we learned that in order to access a file on the user’s device, we had to use an with the “file” . And in order to create the to upload the file, we had to use a element. <input> type HTTP request <form> When dealing with JavaScript, the first part is still true. We still need the file input to access the files on the device. However, browsers have a that we can use to make HTTP requests without forms. Fetch API I still like to include a form because: : If JavaScript fails for whatever reason, the HTML form will still work. Progressive enhancement I’m lazy: The form will actually make my work easier later on, as we’ll see. With that in mind, for JavaScript to submit this form, I’ll set up a “submit” . event handler const form = document.querySelector('form'); form.addEventListener('submit', handleSubmit); /** @param {Event} event */ function handleSubmit(event) { // The rest of the logic will go here. } Throughout the rest of this post, we’ll only be looking at the logic within the event handler function, . handleSubmit So the first thing I need to do in this submit handler is call the event’s method to stop the browser from reloading the page to submit the form. preventDefault I like to put this at the end of the event handler so that if there is an thrown within the body of this function, will be called, and the browser will fall back to the default behavior. exception preventDefault not /** @param {Event} event */ function handleSubmit(event) { // Any JS that could fail goes here event.preventDefault(); } Next, we’ll want to construct the HTTP request using the Fetch API. The Fetch API expects the and a second, . first argument to be a URL optional argument as an Object We can get the URL from the form’s property. It’s available on any which we can access using the event’s property. If the is not defined in the HTML, it will default to the browser’s current URL. action form DOM node currentTarget action /** @param {Event} event */ function handleSubmit(event) { const form = event.currentTarget; const url = new URL(form.action); fetch(url); event.preventDefault(); } Relying on the HTML to define the URL makes it more declarative, keeps our event handler reusable, and our JavaScript bundles smaller. It also maintains functionality if JavaScript fails. By default, Fetch sends HTTP requests using the method, but to upload a file, we need to use a method. We can change the method using ‘s optional second argument. GET POST fetch I’ll create a variable for that object and assign the property, but once again, I’ll grab the value from the form’s attribute in the HTML. method method const url = new URL(form.action); /** @type {Parameters<fetch>[1]} */ const fetchOptions = { method: form.method, }; fetch(url, fetchOptions); Now the only missing piece is actually including the payload in the body of the request. If you’ve ever created a Fetch request in the past, you may have included the body as a or a object. Unfortunately, neither of those will work to send a file, as they don’t have access to the binary file contents. JSON string URLSearchParams Fortunately, there is the browser API. We can use it to construct the request body from the form DOM node. And conveniently, when we do so, it even sets the request’s header to ; also a necessary step to transmit the binary data. FormData Content-Type multipart/form-data const url = new URL(form.action); const formData = new FormData(form); /** @type {Parameters<fetch>[1]} */ const fetchOptions = { method: form.method, body: formData, }; fetch(url, fetchOptions); That’s really the bare minimum needed to upload files with JavaScript. Let’s do a little recap: Access to the file system using a file type input. Construct an HTTP request using the Fetch (or ) API. XMLHttpRequest Set the request method to . POST Include the file in the request body. Set the HTTP header to . Content-Type multipart/form-data Today, we looked at a convenient way of doing that, using an HTML form element with a submit event handler, and using a object in the body of the request. The current function should look like this. FormData handleSumit /** @param {Event} event */ function handleSubmit(event) { const url = new URL(form.action); const formData = new FormData(form); /** @type {Parameters<fetch>[1]} */ const fetchOptions = { method: form.method, body: formData, }; fetch(url, fetchOptions); event.preventDefault(); } Unfortunately, the current submit handler is not very reusable. Every request will include a body set to a object and a “ ” header set to . This is too brittle. FormData Content-Type multipart/form-data Bodies are not allowed in requests, and we may want to support different content types in other POST requests. GET We can make our code more robust to handle and requests, and send the appropriate header. GET POST Content-Type We’ll do so by creating a object in addition to the , and running some logic based on whether the request method should be or . I’ll try to lay out the logic below: URLSearchParams FormData POST GET Is the request using a method? POST Yes: is the form’s attribute ? enctype multipart/form-data Yes: set the body of the request to the object. The browser will automatically set the “ ” header to . FormData Content-Type multipart/form-data No: set the body of the request to the object. The browser will automatically set the “ ” header to . URLSearchParams Content-Type application/x-www-form-urlencoded No: We can assume it’s a request. Modify the URL to include the data as query string parameters. GET The refactored solution looks like this: /** @param {Event} event */ function handleSubmit(event) { /** @type {HTMLFormElement} */ const form = event.currentTarget; const url = new URL(form.action); const formData = new FormData(form); const searchParams = new URLSearchParams(formData); /** @type {Parameters<fetch>[1]} */ const fetchOptions = { method: form.method, }; if (form.method.toLowerCase() === 'post') { if (form.enctype === 'multipart/form-data') { fetchOptions.body = formData; } else { fetchOptions.body = searchParams; } } else { url.search = searchParams; } fetch(url, fetchOptions); event.preventDefault(); } I really like this solution for a number of reasons: It can be used in any form. It relies on the underlying HTML as the declarative source of configuration. The HTTP request behaves the same as with an HTML form. This follows the principle of progressive enhancement, so file upload works the same when JavaScript is working properly or when it fails. So, that’s it. That’s uploading files with JavaScript. I hope you found this useful and plan to stick around for the whole series. In the next post, we’ll move to the back end to see what we need to do to receive files. Upload files with HTML Upload files with JavaScript Receiving file uploads with Node.js (Nuxt.js) Optimizing storage costs with Object Storage Optimizing delivery with a CDN Securing file uploads with malware scans Thank you so much for reading. If you liked this article, please . It's one of the best ways to support me. You can also or if you want to know when new articles are published. share it , sign up for my newsletter follow me on Twitter Also published . here
