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

cloudflare-mysql

v0.9.4

Published

A Cloudflare Workers compatible MySQL package based on the MySQL Node package.

Downloads

8

Readme

cloudflare-mysql

This is a modification to the MySQL JavaScript package which removes the node dependencies and refactors it for use in Cloudflare Workers.

Alongside the node dependency removals, two polyfills are provided, but only to the point that they're functional in this package. That is to say, they're not 100% polyfill covers, they're only a polyfill for the mysql package.

Getting started

Understanding the downsides

A major downside is that each request to your worker, will initialize one new connection. Connections cannot be stored in the memory. This will cause a much heavier impact on your MySQL server than if you'd only have server replicas running constantly.

If you're starting a new project,

then I advise you strongly to pick a serverless approach, such as Cloudflare D1 (Open Alpha) or Turso: SQLite Developer Experience in an Edge Database.

Using the package

Using the package is no different than using the original package, all you have to do is remove any dependencies to the previous package:

npm uninstall mysql @types/mysql

And add the this package:

npm install cloudflare-mysql

And change the imports from mysql to cloudflare-mysql.

Types are automatically included. The types are the same as @types/mysql, at the forked point. I will continue to provide patches to this package if the original package is at some point updated.

Example

import { createConnection } from "cloudflare-mysql";

export default {
  async fetch(request: Request, env: Env, context: ExecutionContext): Promise<Response> {
    const url = new URL(request.url);
    const searchInput = url.searchParams.get("search");

    const result = await new Promise<any>((resolve) => {
      const connection = createConnection({
        host: "localhost",
        user: "root",
        password: "password",
        database: "database"
      });

      connection.connect((error) => {
        if(error)
          throw new Error(error.message);

        connection.query("SELECT title FROM articles WHERE title LIKE CONCAT('%', ?, '%')", [ searchInput ], (error, rows, fields) => {
          connection.end();
          
          resolve({ fields, rows });
        });
      });

    });

    return new Response(JSON.stringify(result, undefined, 4));
  }
}

/*
  {
    "fields": [
      {
        "catalog": "def",
        "db": "developer_blog",
        "table": "articles",
        "orgTable": "articles",
        "name": "title",
        "orgName": "title",
        "charsetNr": 33,
        "length": 765,
        "type": 253,
        "flags": 4097,
        "decimals": 0,
        "zeroFill": false,
        "protocol41": true
      }
    ],
    "rows": [
      {
        "title": "Restricting a Google Maps API key"
      }
    ]
  }
 */

There is also a full worker example that you can try locally or remotely.