open-index/open-npm huggingface dataset:
npm package: @sabbam/fluxcss
Description: Next-generation CSS framework combining utility-first approach, pre-styled components, and advanced animations
Author: FluxCSS Team
Latest version: 1.0.0

# FluxCSS

A next-generation CSS framework that combines the utility-first approach of Tailwind, the pre-styled components of Bootstrap, and the animation capabilities of GSAP.

## Features

- **Utility-First**: Comprehensive utility classes for rapid development
- **Pre-styled Components**: Ready-to-use components like buttons, cards, modals, and more
- **Advanced Animations**: GSAP-powered animations and scroll triggers
- **Modern CSS**: Container queries, glassmorphism, neumorphism, and 3D transforms
- **Mobile-First**: Responsive design with mobile-first approach
- **Accessibility**: Built-in accessibility features and focus management
- **Dark Mode**: Complete dark mode support
- **Tree-shakeable**: Only include the CSS you need

## Installation

```bash
npm install fluxcss
```

## Usage

### CSS Import

```css
@import 'fluxcss/dist/fluxcss.css';
```

### HTML

```html
<!DOCTYPE html>
<html>
<head>
  <link rel="stylesheet" href="node_modules/fluxcss/dist/fluxcss.css">
</head>
<body>
  <div class="fx-card fx-shadow-lg">
    <div class="fx-card-header">
      <h3 class="fx-card-title">Hello FluxCSS</h3>
    </div>
    <div class="fx-card-body">
      <p class="fx-card-text">This is a beautiful card component!</p>
      <button class="fx-btn fx-btn-primary">Get Started</button>
    </div>
  </div>
</body>
</html>
```

## Quick Start

### Buttons

```html
<button class="fx-btn fx-btn-primary">Primary Button</button>
<button class="fx-btn fx-btn-secondary">Secondary Button</button>
<button class="fx-btn fx-btn-outline">Outline Button</button>
<button class="fx-btn fx-btn-ghost">Ghost Button</button>
```

### Cards

```html
<div class="fx-card fx-shadow-lg">
  <div class="fx-card-header">
    <h3 class="fx-card-title">Card Title</h3>
  </div>
  <div class="fx-card-body">
    <p class="fx-card-text">Card content goes here.</p>
  </div>
  <div class="fx-card-footer">
    <button class="fx-btn fx-btn-primary">Action</button>
  </div>
</div>
```

### Animations

```html
<div class="fx-fade-in fx-scroll-reveal">
  <h2>Animated Content</h2>
</div>
```

## Documentation

Visit our [documentation site](https://fluxcss.dev) for complete guides and examples.

## License

MIT License - see [LICENSE](LICENSE) file for details.

## Contributing

We welcome contributions! Please see our [Contributing Guide](CONTRIBUTING.md) for details.

## Support

- [GitHub Issues](https://github.com/fluxcss/fluxcss/issues)
- [Discord Community](https://discord.gg/fluxcss)
- [Documentation](https://fluxcss.dev)
npm package: @sabbatical/a2-config-service
Description: A configuration service for Angular2 apps
Author: Peter Snider
Latest version: 0.3.2

# a2-config-service

This consists of a server module and an Angular2 service.
The server module supports setting multiple web-app configurations.

When a web app requests the config.service.js javascript file (which contains the Angular2 ConfigurationService),
the server selects the configuration for that user, based on what is in the session,
and sends javascript for the ConfigurationService that contains the selected configuration.

This provides all of the configuration data in the service itself, so it may be used immediately.

The service has one default configuration.
If you have multiple configurations, you must set one of them as the default.


# usage

- npm install @sabbatical/a2-config-service
- Define your browser configurations.  
Follow the examples in config/browser-*  
You may place these files anywhere in your project, since they are referenced directly by your server.


## Add to your web server
- import the package
```
import {addConfiguration as addBrowserConfiguration, handleConfigServiceJS} from '@sabbatical/a2-config-service/server'
```
- add each of your browser configurations to your server  
```
// The first configuration is the default, unless the is_default parameter is set
addBrowserConfiguration('beta', common, beta)
addBrowserConfiguration('alpha', common, alpha)
```
- serve the config.service.js file from the path that your web-app uses  
```
app.get('/yourwebapp/config.service.js', handleConfigServiceJS)
```


## Add to the ConfigurationService to your web-app
- import the service into any of your web-app's files that reference it    
```
import { ConfigurationService } from '@sabbatical/a2-config-service/browser';
```
- add the service to your web-app's NgModule's providers  
```
  providers: [
    ConfigurationService,
  ],
```
- inject the service into any components or services that need it  
```
constructor(private configService: ConfigurationService) {
    this.config_str = configService.getConfiguration('b:api_prefix')
}
```

# build
```
npm run build
```

# test
There are no automated tests yet.

Instead, run the server and vist http://localhost:3110/
The page should show:
> b:api_prefix=/api/beta/b
npm package: @sabbatical/configure-local
Description: Manage node.js instance environment configuration.
Author: Peter Snider
Latest version: 1.0.4

# configure-local

- TypeScript 2.0 targeting es6
- Node.js 6

## Summary
This module wraps [**nconf**](https://github.com/indexzero/nconf), and provides a fixed policy of:  
- Use project local configuration files, in the ./config directory, to configure a node instance.
- The configuration files match the name of the instance environment specified by the NODE_ENV environment variable.
- Shared configuration is in common.json.
- The precedence of the configuration sources is:
  - command line arguments  
  Configuration settings passed on the command line override any other settings.
  - environment variables  
  Configuration settings set in environment variables override any settings in configuration files.
  - the instance environment specific configuration file  
  Configuration settings set in an environment specific configuration file override any settings in the common configuration file.
  - the common configuration file  
  Configuration settings in the common configuration file are used when none of the other sources specify a setting.

## Examples
See the [tests](./configure-local.tests.ts)

## Usage

Assuming that you have three instance environments: *development*, *qa*, and *production*
You would then have these files:
- ./config/common.json  
- ./config/development.json
- ./config/production.json
- ./config/qa.json


To configure a module:
```
configure = require('@sabbatical/configure-local')
```
The configuration is loaded the first time *configure-local* is *require*'d.


To get the values of configuration parameters, use get() as in [**nconf**](https://github.com/indexzero/nconf):
```
configure.get()   // returns the entire configuration
configure.get('a:b')  // returns the value or object that would be accessed by ['a']['b']
```

To reload the configuration:
```
configure.reloadConfig()
```
Subsequent calls to configure.get will return updated values.

## Setup for Build
```
npm install
```

## Build
Build the software:  
```
npm run build
```

Remove the generated files:
```
npm run clean
```

## Test
Run the tests:  
```
npm run test
```

## Problems?
Please report them as issues on the [GitHub repo](https://github.com/psnider/configure-local).
npm package: @sabbatical/document-database
Description: Interface to a generic document (no-SQL) database.
Author: Peter Snider
Latest version: 0.5.4

# document-database-if

Interface to a generic document (no-SQL) database.  
See the **DocumentDatabase** type in the [declarations file](./document-database.d.ts).

## adaptors

- [InMemoryDB](https://www.npmjs.com/package/@sabbatical/in-memory-db)  
An in-memory database, that doesn't persist its data.  
This is great for testing.
- [MongoDBApaptor](https://www.npmjs.com/package/@sabbatical/mongoose-adaptor)  
For use with a mongoDB database, using mongoose.js for schema enforcement.  
We use this for initial databases.


# tests
There are tests for this interface in the [tests](./tests) sub-package, that can be configured for use with any DocumentDatabase-compliant object.

To use these tests for you own database adaptor, 
install these packages to your database adaptor package:
- chai
- mocha
- @sabbatical/document-database/tests

and add these dependencies to the *compilerOptions.types* field of your tsconfig.json file:
```
    "compilerOptions": {
        "types" : ["chai", "mocha", "@psnider/document-database/tests"]
```
npm package: @sabbatical/drop-root-privileges
Description: Set the privileges of a program to a given user and group.
Author: Peter Snider
Latest version: 0.1.0

# drop-root-privileges

Changes the user and group permissions for the caller (running as root).
Calls process.exit() if the permissions cannot be changed.

Use this to drop permissions for a server that was started with root privileges (in order to open up a privileged port).

# usage
```
let uid = 'myserveruser'
let gid = 'myservergroup'
dropRootPrivileges({uid, gid})
```

Optionally, you can add a [pino]()-compatible logger with:
```
import {Logger} from 'pino'
var log: Logger
dropRootPrivileges({uid, gid}, log)
```


# build
```
npm run build
```

# test
This has no tests yet.
npm package: @sabbatical/generic-data-server
Description: The portion of a micro-service that manages a database of a single document type.
Author: Peter Snider
Latest version: 0.4.6

# generic-data-server

An in-memory database that implements [document-database-if](https://github.com/psnider/document-database-if).

This database is for test only, as it doesn't persist.

This is used in [people-service](https://github.com/psnider/people-service)

## problems
The tests use promisify-node, which has a bug when using es6 classes.  
See: https://github.com/nodegit/promisify-node/issues/26

If you are developing this package, then run ```npm run patch-promisify-node``` after you run npm install.

This does not affect the *generic-data-server* package itself.

## build
```
npm run build
```

## test
```
npm run test
```

This now checks for an existing *mongod* instance on port 27016.
If there is one, the test will fail, and you will see output from *npm* such as:
```
> ! lsof -i :27016
COMMAND   PID  USER   FD   TYPE            DEVICE SIZE/OFF NODE NAME
mongod  21830 peter    5u  IPv4 0xaa2260c34917de20      0t0  TCP *:27016 (LISTEN)
```
in which case, you should stop the other instance of mongod. Carefully!

## debugging
Often, it is enough to just enable logging, which is off by default to keep the test output clean.
In the *test-only* script, change DISABLE_LOGGING to:
```
DISABLE_LOGGING=false
```

You may use source-level debugging in MicroSoft Visual Studio Code by selecting launch config *Mocha* from debug mode.
npm package: @sabbatical/git-get-commit-id
Description: get the git commit-id for the current directory.
Author: Peter Snider
Latest version: 1.1.2

# git-get-commit-id
## Summary
This module determines the git commit-id for the repo in the current directory.


## Usage


To check whether a git workspace is clean:
```
var git = require('./git-get-commit-id');

git.getGitStatus((error, results) => {
    console.log(`this workspace is ${results.is_clean ? '' : 'not'} clean`)
})
```

To get the commit-id:
```
git.getGitCommitID(function (error, results) {
    console.log(`git commit-id=${results.id}`);
});
```

You can check the other parameters for error and other information, if needed.


## Setup for Build
```
npm install
```

## Build
Build the software:  
```
npm run build
```

Remove the generated files:
```
npm run clean
```

## Test
Run the tests:  
```
npm run test
```

## Problems?
Please report them as issues on the GitHub repo.
npm package: @sabbatical/in-memory-db
Description: An in-memory database that implements the document-database interface. This database is for test only, as it doesn't persist.
Author: Peter Snider
Latest version: 0.3.6

# in-memory-db

An in-memory database that implements [document-database](https://github.com/psnider/document-database).

This database is for test only, as it doesn't persist.

This is used in [people-service](https://github.com/psnider/people-service)

## build
```
npm run build
```

## test
```
npm run test
```
npm package: @sabbatical/mongoose-adaptor
Description: A database adaptor for using MongoDB with mongoose.js.
Author: Peter Snider
Latest version: 0.5.3

# mongoose-adaptor

A database adapator for MongoDB using mongoose.js.
This adaptor is compatible with the document-database interface.

# install

```
npm install
```


# build

```
npm run build
```


# test

```
npm run test
```
npm package: @sabbatical/process-spawner
Description: Spawn a process, with some common control options.
Author: Peter Snider
Latest version: 0.2.3

# process-spawner

## Summary
Spawn a process, with some common control options.

## Usage

See the [tests](./process-spawner.tests.ts)

Here is an example from the "should run the process" test:
```
var request = require('request')
var process_spawner = require('./process-spawner')
var ProcessSpawner = process_spawner.ProcessSpawner

let ps = new ProcessSpawner({
    program: 'node',
    args: ['test-simple-server-for-test.js']
})
var promises = ps.start()
promises.ready.then(() => {
    request.get('http://localhost:7341', (error, response, body) => {
        if (!error && response.statusCode == 200) {
            console.log(body)
        } else {
            if (!error) {
                error = new Error(`response.statusCode=${response.statusCode}`)
            }
            console.log(`error=${error}`)
        }
        ps.stop().then(() => {
            console.log('stopped the process')
        })
    })
})
```


## Setup for Build
```
npm install
```

## Build
Build the software:  
```
npm run build
```

Remove the generated files:
```
npm run clean
```

## Test
Run the tests:  
```
npm run test
```

## Problems?
Please report them as issues on the GitHub repo.
npm package: @sabbatical/server-status
Description: Status shared by all servers. Used for reporting and admin.
Author: Peter Snider
Latest version: 0.1.2

# server-status

General server system status, with an update function.

# usage
```
var status: ServerStatus = {
    server_name: 'some-server',
    version: '0.1.2',
    git_commit_id: 'abcd'
    latest_restart: new Date()
}
udpateServerStatus(status)
```

We use [@sabbatical/git-get-commit-id](https://www.npmjs.com/package/@sabbatical/git-get-commit-id) to set the *git_commit_id*.


# build
```
npm run build
```

# test
This has no tests yet.
npm package: @sabbirshouvo/un-source-map
Description: Unpack your JS source maps to original files and folders in a proper way.
Author: Sabbir Hasan
Latest version: 1.0.2

[![npm version](https://badge.fury.io/js/@sabbirshouvo%2Fun-source-map.svg)](https://badge.fury.io/js/@sabbirshouvo%2Fun-source-map)
[![GitHub issues](https://img.shields.io/github/issues/sh-sabbir/un-source-map)](https://github.com/sh-sabbir/un-source-map/issues)
[![GitHub stars](https://img.shields.io/github/stars/sh-sabbir/un-source-map)](https://github.com/sh-sabbir/un-source-map/stargazers)
[![GitHub forks](https://img.shields.io/github/forks/sh-sabbir/un-source-map)](https://github.com/sh-sabbir/un-source-map/network)
[![Twitter](https://img.shields.io/twitter/url?style=social&url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40sabbirshouvo%2Fun-source-map)](https://twitter.com/intent/tweet?text=Wow:&url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2F%40sabbirshouvo%2Fun-source-map)

# Un-Source-Map (unmap)

### CLI to Unpack your JS source maps to original files and folders in a proper way.  


## Install
npm:
```shell
npm install -g @sabbirshouvo/un-source-map
```
yarn:
```shell
yarn global add  @sabbirshouvo/un-source-map
```

## Usage
```shell
unmap [options] [source]
```

`source` is a required parameter, it can also be a directory.

If `source` is a directory, `unmap` will traverse all the files in this directory and deal each file.

## Examples

```shell
unmap bundle.js.map
unmap bundle.js.map -o app
```