
Security News
Insecure Agents Podcast: Certified Patches, Supply Chain Security, and AI Agents
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.
atom-selected-requires
Advanced tools
Retrieve the paths of any require statements in the current selection.
Retrieve the paths of any require statements in the current selection. Originally extracted from atom-node-resolver, and syntax-aware, just like browserify.
paths = selectedRequires([editor])Given an editor, check all of the current selections and return an array of require paths. If no editor is
supplied, the currently active editor will be used.
For example, given a file like so:
const a = require('atom-selected-requires')
const b = require('@scoped/package')
const c = require('./local-file')
You could run the following:
const selectedRequires = require('atom-selected-requires')
const editor = atom.workspace.getActiveEditor()
console.log(selectedRequires(editor))
And receive an array like so in return:
[
'atom-selected-requires',
'@scoped/package',
'./local-file'
]
MIT. See LICENSE.md for details.
FAQs
Retrieve the paths of any require statements in the current selection.
We found that atom-selected-requires demonstrated a not healthy version release cadence and project activity because the last version was released 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
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.

Security News
Tailwind Labs laid off 75% of its engineering team after revenue dropped 80%, as LLMs redirect traffic away from documentation where developers discover paid products.

Security News
The planned feature introduces a review step before releases go live, following the Shai-Hulud attacks and a rocky migration off classic tokens that disrupted maintainer workflows.