canirequire › CommonJS › karma-phantomjs-launcher
Is karma-phantomjs-launcher ESM-only? Can you require() it?
A Karma plugin. Launcher for PhantomJS.
Last verified Sep 9, 2026 against karma-phantomjs-launcher@1.0.4. Markdown · JSON
CommonJS CommonJS on paper — require() failed in our runtime test
karma-phantomjs-launcher declares a CommonJS entry only, but require("karma-phantomjs-launcher") failed on every Node.js version in our probe: ERR_INVALID_ARG_TYPE. import "karma-phantomjs-launcher" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.
What to do
- require("karma-phantomjs-launcher") failed in our probe on every Node.js version (ERR_INVALID_ARG_TYPE); check the package README for peer dependencies or setup before relying on it.
- From ES modules use the default import: import karmaPhantomjsLauncher from "karma-phantomjs-launcher"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: no types are available for karma-phantomjs-launcher; declare the module yourself if you need them.
- This package is deprecated: PhantomJS development have stopped, use puppeteer or similar
Deprecated: PhantomJS development have stopped, use puppeteer or similar
Does karma-phantomjs-launcher@1.0.4 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("karma-phantomjs-launcher") from a CommonJS file and import "karma-phantomjs-launcher" from an ES module.
| Runtime | require("karma-phantomjs-launcher") | import "karma-phantomjs-launcher" |
|---|---|---|
| Node.js 18 | ✗ failsERR_INVALID_ARG_TYPE | ✗ failsERR_INVALID_ARG_TYPE |
| Node.js 20 | ✗ failsERR_INVALID_ARG_TYPE | ✗ failsERR_INVALID_ARG_TYPE |
| Node.js 22 | ✗ failsERR_INVALID_ARG_TYPE | ✗ failsERR_INVALID_ARG_TYPE |
| Node.js 24 | ✗ failsERR_INVALID_ARG_TYPE | ✗ failsERR_INVALID_ARG_TYPE |
| Node.js 26 | ✗ failsERR_INVALID_ARG_TYPE | ✗ failsERR_INVALID_ARG_TYPE |
| Bun 1.4.0 | ✗ failsERR_INVALID_ARG_TYPE | ✗ failsERR_INVALID_ARG_TYPE |
A failing require() on a CommonJS package usually means the package needs a browser/DOM global, a peer dependency, or a native binary that is not available in a bare Node.js process.
How to import karma-phantomjs-launcher
ES modules (import)
import karmaPhantomjsLauncher from "karma-phantomjs-launcher";Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.
CommonJS (require)
// require("karma-phantomjs-launcher") failed in our probe on every Node.js version we test (ERR_INVALID_ARG_TYPE); see the runtime table.
const karmaPhantomjsLauncher = require("karma-phantomjs-launcher");Module format by version
Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (17 versions; the newest 17 shown).
| Versions | Format | First published |
|---|---|---|
| 0.0.1 – 1.0.4 | CommonJS | Mar 19, 2013 |
Frequently asked
Is karma-phantomjs-launcher ESM-only?
karma-phantomjs-launcher@1.0.4 declares a CommonJS entry, but require() fails at runtime. karma-phantomjs-launcher declares a CommonJS entry only, but require("karma-phantomjs-launcher") failed on every Node.js version in our probe: ERR_INVALID_ARG_TYPE. import "karma-phantomjs-launcher" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.
Can I require karma-phantomjs-launcher?
Not in practice. karma-phantomjs-launcher declares a CommonJS entry, but require("karma-phantomjs-launcher") failed on every Node.js version in our probe: ERR_INVALID_ARG_TYPE. Check the package README for peer dependencies or setup before relying on it.
Can I import karma-phantomjs-launcher with ES module syntax?
Yes. import karmaPhantomjsLauncher from "karma-phantomjs-launcher" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.
Does karma-phantomjs-launcher work in Bun?
Importing karma-phantomjs-launcher failed in Bun 1.4.0 on Sep 9, 2026: TypeError: The "path" property must be of type string, got object
Does karma-phantomjs-launcher ship TypeScript types?
No. karma-phantomjs-launcher ships no type declarations and there is no @types package for it.
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- ember-load-initializers 3.0.1ESM-only
- @react-native-community/eslint-config 3.2.0CommonJS
- gulp-mocha 10.0.1ESM-only
- load-grunt-tasks 5.1.0CommonJS
- @vue/cli-plugin-unit-jest 5.0.9CommonJS
- @storybook/addon-storysource 8.6.14Dual
- broccoli-asset-rev 3.0.0CommonJS
- ember-cli-inject-live-reload 2.1.0CommonJS