You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the package information is cached per file path and a reference to the cached object is included in the caller object that is returned, it is technically possible to change the package information stored against a file. This would most likely be done accidentally but it could, in theory, be done to mask the package origin of a file, to a degree.
The simplest solution is to simply change Finder._buildCaller to create a copy of the cached object (e.g. using Object.assign).
The text was updated successfully, but these errors were encountered:
* roll v0.1.0
* changed version for tmp devDependency to semver range
* resolves#3 by including "column" number in caller information
* fixes#2 by only including copy of package information in caller information
* roll v0.1.1
* start working on 0.2.0
* resolves#5 by adding new filterPackages option to compliment existing excludes option
* #5 documented that filterPackages is only called for packages that are not included in excludes option
* #5 add tests to cover modifications within filterPackages option
* resolves#6 by adding filterFiles option
* #6 corrected minor alignment issue for options table in README
* resolves#7 by returning information for all callers and adding limit option for control over number of callers returned
* resolves#9 by renaming references git repo references to node-knockknock
* resolves#10 by adding offset option to control initial call stack offset
* fixes#11 by excluding all calls from the start of the stack from within the originator module
* roll v0.2.0
* bumped devDependencies
As the package information is cached per file path and a reference to the cached object is included in the caller object that is returned, it is technically possible to change the package information stored against a file. This would most likely be done accidentally but it could, in theory, be done to mask the package origin of a file, to a degree.
The simplest solution is to simply change
Finder._buildCaller
to create a copy of the cached object (e.g. usingObject.assign
).The text was updated successfully, but these errors were encountered: