open-index/open-npm huggingface dataset:
npm package: @signalapp/windows-dummy-keystroke
Description: This package exports `sendDummyKeystroke()`, which will send a generic key down/up event on Windows.
Latest version: 1.0.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Windows Dummy Keystroke

This package exports `sendDummyKeystroke()`, which will send a generic key down/up event on Windows.

## But why?

This is a workaround for an issue with Windows Notifications. Normally [you can call the native `AllowSetForegroundWindow` method to permit another application to take foreground focus](https://devblogs.microsoft.com/oldnewthing/20090220-00/?p=19083). But when an app is started from a Windows notification activation, this call fails with `ERROR_ACCESS_DENIED`. One of a [list of conditions has to be met](https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-allowsetforegroundwindow) for the call to succeed.

Sending a key press event satisfies this check and lets `AllowSetForegroundWindow` succeed.

This is useful for letting a second instance of a program activate the original instance. In Electron, you would call this before calling `requestSingleInstanceLock()`, as this can call `AllowSetForegroundWindow` for the initial instance.

This workaround was [used by Chromium to solve a foreground focus issue](https://bugs.chromium.org/p/chromium/issues/detail?id=837796), and is adapted here for use with Node.
npm package: @signalchain/minusql
Description: A GraphQL client library for fetching & caching data.
Author: Todo
Latest version: 0.3.0

# MinusQL

A lightweight GraphQL client with builtin caching.

Requires Node version >=17.8 (native fetch)

## Notes: (Docs coming soon)

Update Query: Is the name of a query as a string. The data returned from the mutation will be appended to current cache data.
npm package: @signalchain/rollup-plugin-env-gen
Description: Config based generation of a `.env` and public variables file. Manage your environment secrets and public application variables from a single JavaScript file.
Latest version: 0.6.0

# @signalchain/rollup-plugin-env-gen

Config based generation of a `.env` and public variables file. Manage your environment secrets and public application variables from a single JavaScript file.

Works with Rollup and Vite.

## Install

`npm i -D @signalchain/rollup-plugin-env-gen`

## Sample Env

Optionally generate a modified version of the source file and produce a `.sample` file. (This is the default, but can be turned off by setting `samplePath` to false.) The sample file is identical to the input file with the exception that variables and secrets are converted to the zero value of their type.

For example:

- "Hello world!" ➡ ""
- 12345 ➡ 0
- true ➡ false

## Public Vars

Public variables, such as those used in client side applications, will be generated only if the exported object has a `publicVars` field. There is a clear boundary at build time between `publicVars` and all other fields. That said, if you import secrets into client side code, they are visible to anyone who wants to poke at the source. So only include variables that are meant to be public in the `publicVars` object.

### Runtime Template Variables

For runtime template strings in Public Env, wrap your template string like this ➡ `"%`YOUR_TEMPLATE_STRING`%"`. Wrapping is required to keep the template string from being evaluated at build time. This feature only makes sense for public vars, so any template string outside of the `publicVars` object will be evaluated at build time.

## Use

```typescript
export type Options = {
	mode?: string // process.env.NODE_ENV
	inputPath?: string // [PROJECT_ROOT]/.env.js
	envPath?: string // [PROJECT_ROOT]/.env
	samplePath?: string | boolean // [PROJECT_ROOT]/.env.sample.js
	publicPath?: string // [PROJECT_ROOT]/src/publicVars.js
	watch?: boolean // true (WIP)
}

// rollup.config.js || vite.config.js
plugins: [envGen(Options)]
```

The `inputPath` defaults to `[PROJECT_ROOT]/.env.js`. That file exports a default object with a set of keys that will be used to match the `mode` option on build. If the `publicVars` key is in the exported object from the `inputPath`, it will generate a `publicVars.js` file at the `publicPath`. (Defaults to `[PROJECT_ROOT]/src/publicVars.js`.)

## Example

```js
// .env.js

const shared = {
	BOTH: true,
}

const development = {
	...shared,
	TEST: true,
}

const production = {
	...shared,
	TEST: false,
}

const sharedPublic = {
	PUBLIC: true,
}

const publicVars = {
	development: {
		...sharedPublic,
		TEMPLATED_TEMPLATE: "%`${window.location.host}`%",
	},
	production: {
		...sharedPublic,
	},
}

export default {
	development,
	production,
	publicVars,
}
```

## .gitignore

If you don't want to commit your secrets to git, add the following to your `.gitignore`

```txt
# environment variables files
.env
.env*
!.env.sample.js
```

This says, "don't commit `.env` or `.env<any other text>`, but do commit `.env.sample.js`"
npm package: @signalchain/rollup-plugin-theme-engine
Description: [WIP]
Author: James Gleason
Latest version: 0.9.5

# Theme Engine

[WIP]

## Install

`npm i -D @signalchain/rollup-plugin-theme-engine`

## NPM

[https://www.npmjs.com/package/@signalchain/rollup-plugin-theme-engine](https://www.npmjs.com/package/@signalchain/rollup-plugin-theme-engine)