Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
semver-try-require
Advanced tools
micro module to require or import (versions of) modules that might not be there
A micro module that helps you require or import (versions of) modules that might not be there.
Useful to test for the availability of optional and peer dependencies before working with them.
See ESM below if you're using this in an ESM only context.
So you made the typescript compiler (v2) an optional dependency. But you just want to keep running if it ain't there.
Do this:
const tryRequire = require("semver-try-require");
// import typescript if there's a version >= 2 available
const typescript = tryRequire("typescript", ">=2");
// now you can test if typescript is actually there
const lProgram = "const cube = x => x*x*x; console.log(cube(42))";
if (typescript !== false) {
console.log(typescript.transpileModule(lProgram, {}).outputText);
// Result:
// var cube = function (x) { return x * x * x; };
// console.log(cube(42));
} else {
// typescript >=2 not found - use fallback
console.log(lProgram);
// Result:
// const cube = x => x*x*x; console.log(cube(42))
}
In ESM it's almost the same, except there dynamic imports are always
asynchronous, so you'll have to await
it (or use promises):
import tryImport from "semver-try-require";
// import typescript if there's a version >= 5 available.
const typescript = await tryImport("typescript", >=5);
// now you can test if typescript is actually there
const lProgram = "const cube = x => x*x*x; console.log(cube(42))";
if (typescript !== false) {
console.log(typescript.transpileModule(lProgram, {}).outputText);
// Result:
// var cube = function (x) { return x * x * x; };
// console.log(cube(42));
} else {
// typescript >=5 not found - use fallback
console.log(lProgram);
// Result:
// const cube = x => x*x*x; console.log(cube(42))
}
This module started to try a few non-run-of-the-mill things with the
npm registry (deprecate, beta publishing, renaming). The tryRequire
function in
dependency-cruiser
seemed like a good candidate as it was not a thing that'd be unique
to dependency-cruiser, and would probably be easier to maintain on its
own anyway. I named it tigerclaws-try-require
until I realized the
semver check was what distinguished it from the other try-require
like npm modules out there.
dependency-cruiser now uses semver-try-require in the transpiler wrappers and it enables it to cruise typescript, coffeescript and livescript code without having to ship the heavy duty compilers for these languages.
Made with :metal: in Holland
FAQs
micro module to require or import (versions of) modules that might not be there
The npm package semver-try-require receives a total of 249,644 weekly downloads. As such, semver-try-require popularity was classified as popular.
We found that semver-try-require demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.