open-index/open-npm huggingface dataset:
npm package: @lqcoder/axios
Description: ts 实现 对 xhr 封装 实现 axios 使用 vite 打包发布
Latest version: 0.0.2

## 介绍

ts 实现 对 xhr 封装 实现 axios
使用 vite 打包发布

使用例子 vue3：

```
<script lang="ts" setup>
import { ref } from 'vue'
import axios from '@lqcoder/axios'


//测试 下载 进度条

const progress = ref('0')

//测试 上传文件进度条
const fileRef = ref<HTMLInputElement | null>()
let file: File

const handle = () => {
  if (fileRef.value && fileRef.value.files) {
    file = fileRef.value.files[0]
  }
}

const upload = () => {
  if (!file) alert('未选择文件')
  let formData = new FormData()
  formData.append('file', file)
  axios({
    method: 'post',
    url: 'api/uploadFile',
    data: formData,
    onUploadProgress(e) {
      console.log(3333333, e)
      progress.value = (e.loaded / e.total).toFixed(2)
    }
  })

}


</script>

<template>
  <section>app====下载进度{{ progress }}</section>
  <section>
    选择文件
    <input ref="fileRef" type="file" accept="*" @change="handle" />
  </section>
  <button @click="upload">上传文件</button>
</template>

```
npm package: @lqh-notes/local-client
Description: This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
Latest version: 1.0.0

# Getting Started with Create React App

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

## Available Scripts

In the project directory, you can run:

### `npm start`

Runs the app in the development mode.\
Open [http://localhost:3000](http://localhost:3000) to view it in the browser.

The page will reload if you make edits.\
You will also see any lint errors in the console.

### `npm test`

Launches the test runner in the interactive watch mode.\
See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.

### `npm run build`

Builds the app for production to the `build` folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.\
Your app is ready to be deployed!

See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.

### `npm run eject`

**Note: this is a one-way operation. Once you `eject`, you can’t go back!**

If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

## Learn More

You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).

To learn React, check out the [React documentation](https://reactjs.org/).
npm package: @lqiong/gs
Description: a repo to start with atomico
Latest version: 1.0.1

# base

Welcome to [Atomico](https://github.com/atomicojs/atomico) as an [author](https://twitter.com/uppercod), I hope your experience of use is memorable!

this configuration provides you with a structure to start with Atomico in an agile way thanks to [bundle-cli](https://github.com/atomicojs/bundle-cli), with this configuration you will be able to:

**1.-** Documentar y desarrollar desde un fichero markdown o html , **bundle-cli se encargara de extraer sus script, estilos y otros desde ficheros markdown o html**, eg:

```markdown
# Atomico size is less than 4kb

and I'm a markdown file ...

<!--
Now some magic of bundle-cli, bundle-cli extract
the [src] of the tags and export the scripts to Rollup and more.
-->

<my-component></my-component>

<script src="./my-component.js" type="module"></script>
```

> In summary an effect similar to MDX but with Markdown.

**2.-** **LiveReload, local server and an incremental file watcher**, If you create a new markdown or html file, it will be added to the export queue to be viewed on the local server. Likewise, the changes associated with the exported files will refresh the browser automatically (LiveReload).

**3.-** Easily export all your components and hooks in separate files.

### Scripts

`npm start`: Create a Server + LiveReload for your project, with this you will be able to view all its components from **the port that will be shown by console according to availability**. I hope you like the interface shown by the server

`npm run create:component`: Create a folder inside the `src/components` folder with everything you need to get started with your component, the folder to be created adheres to the Atomico [style guides](https://atomico.gitbook.io/doc/guides/code-style).

`npm run build`: Export the documentation and minify the js code and the associated css.

`npm run build:all`: Export all files that comply with the expression `src/**/**/*-*.js;`, under Atomico [style guides](https://atomico.gitbook.io/doc/guides/code-style) their components and hooks will be automatically exported

## Other resources of interest

1. [Atomico Documentation](https://github.com/atomicojs/atomico).
2. [Atomico Style Guides](https://atomico.gitbook.io/doc/guides/code-style).
3. Twitter of [Atomico](https://twitter.com/atomicojs) and [Autor](https://twitter.com/uppercod)
npm package: @lqiong/wc
Description: a repo to start with atomico
Latest version: 0.0.3

# base

Welcome to [Atomico](https://github.com/atomicojs/atomico) as an [author](https://twitter.com/uppercod), I hope your experience of use is memorable!

this configuration provides you with a structure to start with Atomico in an agile way thanks to [bundle-cli](https://github.com/atomicojs/bundle-cli), with this configuration you will be able to:

**1.-** Documentar y desarrollar desde un fichero markdown o html , **bundle-cli se encargara de extraer sus script, estilos y otros desde ficheros markdown o html**, eg:

```markdown
# Atomico size is less than 4kb

and I'm a markdown file ...

<!--
Now some magic of bundle-cli, bundle-cli extract
the [src] of the tags and export the scripts to Rollup and more.
-->

<my-component></my-component>

<script src="./my-component.js" type="module"></script>
```

> In summary an effect similar to MDX but with Markdown.

**2.-** **LiveReload, local server and an incremental file watcher**, If you create a new markdown or html file, it will be added to the export queue to be viewed on the local server. Likewise, the changes associated with the exported files will refresh the browser automatically (LiveReload).

**3.-** Easily export all your components and hooks in separate files.

### Scripts

`npm start`: Create a Server + LiveReload for your project, with this you will be able to view all its components from **the port that will be shown by console according to availability**. I hope you like the interface shown by the server

`npm run create:component`: Create a folder inside the `src/components` folder with everything you need to get started with your component, the folder to be created adheres to the Atomico [style guides](https://atomico.gitbook.io/doc/guides/code-style).

`npm run build`: Export the documentation and minify the js code and the associated css.

`npm run build:all`: Export all files that comply with the expression `src/**/**/*-*.js;`, under Atomico [style guides](https://atomico.gitbook.io/doc/guides/code-style) their components and hooks will be automatically exported

## Other resources of interest

1. [Atomico Documentation](https://github.com/atomicojs/atomico).
2. [Atomico Style Guides](https://atomico.gitbook.io/doc/guides/code-style).
3. Twitter of [Atomico](https://twitter.com/atomicojs) and [Autor](https://twitter.com/uppercod)
npm package: @lql-pg/base32
Description: Base32 encoding and decoding functions for PostgreSQL
Latest version: 0.5.0

# @pgpm/base32

RFC4648 Base32 encode/decode in plpgsql

# Usage

```sql
select base32.encode('foo');
-- MZXW6===


select base32.decode('MZXW6===');
-- foo
```

# credits

Thanks to 

https://tools.ietf.org/html/rfc4648

https://www.youtube.com/watch?v=Va8FLD-iuTg

# Development

## start the postgres db process

First you'll want to start the postgres docker (you can also just use `docker-compose up -d`):

```sh
make up
```

## install modules

Install modules

```sh
yarn install
```

## install the Postgres extensions

Now that the postgres process is running, install the extensions:

```sh
make install
```

This basically `ssh`s into the postgres instance with the `packages/` folder mounted as a volume, and installs the bundled sql code as pgxn extensions.

## testing

Testing will load all your latest sql changes and create fresh, populated databases for each sqitch module in `packages/`.

```sh
yarn test:watch
```

## building new modules

Create a new folder in `packages/`

```sh
pgpm init
```

Then, run a generator:

```sh
pgpm generate
```

You can also add arguments if you already know what you want to do:

```sh
pgpm generate schema --schema myschema
pgpm generate table --schema myschema --table mytable
```

## deploy code as extensions

`cd` into `packages/<module>`, and run `pgpm package`. This will make an sql file in `packages/<module>/sql/` used for `CREATE EXTENSION` calls to install your sqitch module as an extension.

## recursive deploy

You can also deploy all modules utilizing versioning as sqtich modules. Remove `--createdb` if you already created your db:

```sh
pgpm deploy awesome-db --yes --recursive --createdb
```