AXO stands for ActiveXObject. And the sole purpose of this library is to
return the ActiveXObject constructor from the environment it's loaded in.
Normally you would just reference the constructor directly by simply mentioning
this constructor in your source file can result in blocking of your
file.
There are 2 ways of tackling this issue:
AXO and never mention it.npm install --save axo
This module makes the assumption that it can be loaded in node.js/commonjs based
environment and exports it self on the module.exports. So using browserify for
the code makes a lot of sense here.
var AXO = require('axo');
new AXO('htmlfile');
MIT
FAQs
Return an ActiveXObject without mentioning it in the source
We found that axo demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.