Security News
Fluent Assertions Faces Backlash After Abandoning Open Source Licensing
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
make-synchronized
Advanced tools
[![Build Status][github_actions_badge]][github_actions_link] [![Coverage][coveralls_badge]][coveralls_link] [![Npm Version][package_version_badge]][package_link] [![MIT License][license_badge]][license_link]
Make synchronized functions.
yarn add make-synchronized
This module mainly to support two kinds of different purpose of usage:
Make a module that turns asynchronous function into synchronized
import makeSynchronized from 'make-synchronized'
export default makeSynchronized(import.meta, myAsynchronousFunction)
Make asynchronous functions in an existing module into synchronized
import makeSynchronized from 'make-synchronized'
const synchronized = makeSynchronized(
new URL('./my-asynchronous-function-module.js', import.meta.url),
)
import {
makeSynchronized, // Same as the default export
makeDefaultExportSynchronized,
makeModuleSynchronized,
makeSynchronizedFunction,
makeSynchronizedFunctions,
} from 'make-synchronized'
This module uses MessagePort#postMessage
to transfer arguments, return values, errors between the main thread and the worker. Please make sure the arguments and return values are serializable by the structured clone algorithm.
makeSynchronized(module, implementation)
Make asynchronous functions to be synchronized for export.
If implementation
is a function
, returns a synchronized version of the passed function.
Note: It MUST be used as the default export
// foo.js
import makeSynchronized from 'make-synchronized'
export default makeSynchronized(import.meta, () => Promise.resolve('foo'))
import foo from './foo.js'
foo()
// -> foo
If implementation
is a object
with multiple functions, returns a Proxy
object with synchronized functions attached.
Note: Functions MUST exported as the same name as the key in implementation
object.
// foo-and-bar.js
import makeSynchronized from 'make-synchronized'
export const {foo, bar} = makeSynchronized(import.meta, {
async foo() {
return 'foo'
},
async bar() {
return 'bar'
},
})
import {foo, bar} from './foo-and-bar.js'
foo()
// -> foo
bar()
// -> bar
makeSynchronized(module)
Make asynchronous functions in an existing module to be synchronized to call.
If the passing module
is a module that contains a function type default export, returns a Proxy
function, with other specifiers attached.
// foo.js
export default () => Promise.resolve('default export called')
export const foo = 'foo'
export const bar = () => Promise.resolve('bar called')
const synchronized = makeSynchronized(new URL('./foo.js', import.meta.url))
synchronized()
// -> "default export called"
synchronized.foo
// -> "foo"
// This function also synchronized.
synchronized.bar()
// -> "bar called"
If the passing module
is a module without default export or default export is not a function, a Module
object will be returned with all specifiers.
// foo.js
export const foo = 'foo'
export const bar = () => Promise.resolve('bar called')
import makeSynchronized from 'make-synchronized'
const module = makeSynchronized(new URL('./foo.js', import.meta.url))
module
// [Object: null prototype] [Module] { bar: [Getter], foo: [Getter] }
module.foo
// -> "foo"
module.bar()
// -> "bar called"
makeSynchronizedFunction(module, implementation, specifier?)
Make a synchronized function for export.
Explicit version of makeSynchronized(module, implementation)
that returns the synchronized function for export.
import {makeSynchronizedFunction} from 'make-synchronized'
export default makeSynchronizedFunction(
import.meta,
async () => 'default export called',
)
export const foo = makeSynchronizedFunction(
import.meta,
async () => 'foo export called',
'foo',
)
makeSynchronizedFunctions(module, implementation)
Make synchronized functions for export.
Explicit version of makeSynchronized(module, implementation)
that only returns Proxy
with synchronized functions for export.
import {makeSynchronizedFunctions} from 'make-synchronized'
export const {
// MUST match the key in second argument
foo,
bar,
} = makeSynchronizedFunctions(import.meta, {
foo: async () => 'foo export called',
bar: async () => 'bar export called',
})
makeDefaultExportSynchronized(module)
Make an existing module's default export to be a synchronized function.
Explicit version of makeSynchronized(module)
that only returns the synchronized default export.
import {makeDefaultExportSynchronized} from 'make-synchronized'
const foo = makeModuleSynchronized('foo')
foo()
// -> default export of `foo` module is called.
makeModuleSynchronized(module)
Make an existing module's exports to be synchronized functions.
Synchronize version of import(module)
, always returns a Module
.
- const {default: foo} = await import('foo')
+ const {default: foo} = makeModuleSynchronized('foo')
import {makeModuleSynchronized} from 'make-synchronized'
const {default: foo, bar} = makeModuleSynchronized('foo')
foo()
// -> default export of `foo` module is called.
bar()
// -> `bar` function from `foo` module is called.
FAQs
[![Build Status][github_actions_badge]][github_actions_link] [![Coverage][coveralls_badge]][coveralls_link] [![Npm Version][package_version_badge]][package_link] [![MIT License][license_badge]][license_link]
We found that make-synchronized demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
Research
Security News
Socket researchers uncover the risks of a malicious Python package targeting Discord developers.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.