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.
@marker.io/browser
Advanced tools
npm install -s @marker.io/browser
import markerSDK from '@marker.io/browser';
const widget = await markerSDK.loadWidget({ project: 'abcd1234567890' });
widget.show()
Shows the Marker.io feedback widget.
widget.hide()
Hides the Marker.io feedback widget.
widget.isVisible()
Returns wether the feedback widget is currently visible or not.
widget.capture(mode)
Captures a feedback on the current page.
mode
: Type of capture to trigger. Available modes: fullscreen
, advanced
.
fullscreen
captures the entire visible areaadvanced
shows the advanced capture options: limited area, entire page and desktop.widget.capture(); // or
widget.capture('fullscreen');
widget.capture('advanced');
widget.cancelCapture()
Cancels current capture.
widget.isExtensionInstalled()
Returns a Promise<Boolean>
that indicates if the Marker.io extension has been detected. Having the extension installed allows more accurate screen captures and provides more capture options.
widget.isExtensionInstalled().then((installed) => {
if (installed) {
// ...
} else {
// show install Marker.io extension button
}
});
widget.setReporter(reporterInfo)
Sets the current reporter information given a reporterInfo
object:
reporterInfo.email
: the email address of the reporterreporterInfo.fullName
: the full name of the reporterwidget.setReporter({
email: 'client@website.com',
fullName: 'Gabrielle Rose',
});
widget.clearReporter()
Clears the current reporter information:
widget.clearReporter();
widget.unload()
Unloads and cleans up Marker.io SDK and all used resources.
Marker.io exposes a variety of events that can be listened to using the methods described below.
Usage:
widget.on('eventName', function listener() {
// event handler code
});
'load'
Triggers once Marker.io is loaded.
'loaderror'
Triggers if an error occurs while loading Marker.io.
'beforeunload'
Triggers right before Marker.io unloads.
'show'
Triggers when the feedback button becomes visible.
'hide'
Triggers when the feedback button becomes hidden.
'capture'
Triggers when a feedback is captured.
'feedbackbeforesend'
Triggers before submitting the feedback, i.e. when the user clicks Submit feedback.
'feedbacksent'
Triggers once the feedback is successfully submitted.
'feedbackerror'
Triggers if an error occurs while submitting feedback.
'feedbackdiscarded'
Triggers when the user discards a feedback by clicking on the "Close" button in the widget.
Whenever your application knows about your reporters' identity, you should provide that information through the Marker.io snippet code.
The reporting experience will be much better for your guests as they will not be prompted to provide their contact information while reporting their issues.
Identifying your reporters is dead-simple: all you need to do is to provide their reporter information in the configuration object of your snippet code.
const widget = await markerSDK.loadWidget({
project: '<PROJECT ID>',
reporter: {
email: 'john@clientwebsite.com',
fullName: 'John Smith',
},
});
widget.setReporter()
widget.setReporter({
email: 'john@clientwebsite.com',
fullName: 'John Smith',
});
While Marker.io automatically captures various metadata about the issue (page URL, browser context, console logs, …), it is also possible to pass custom metadata to your issues using the SDK.
For example, this can be useful to help developers debug issues by adding more details about the current state of the application.
Supported types of custom metadata:
const widget = await markerSDK.loadWidget({
project: '<PROJECT ID>',
customData: {
storeId: 123,
storeName: 'Organic Fruits',
},
});
widget.setCustomData()
widget.setCustomData({
product: 'Orange Juice',
price: 3.99,
stock: 130,
});
By default, Marker.io will log some useful information in the console to help you identify configuration problems and better understand how it functions.
However, in certain situations you may want to disable them all together so that it doesn't add noise to your recorded console logs.
To do so, you will need to enable silent mode directly inside your snippet code configuration:
const widget = await markerSDK.loadWidget({
project: '<PROJECT ID>',
silent: true, // <~ Enable silent mode
});
Delay the server-side capture so that your CSS animations can run before the screenshot is taken.
You can enable delayed capture adding a special parameter in your snippet code configuration:
const widget = await markerSDK.loadWidget({
project: '<PROJECT ID>',
// Add the following to delay the server-side rendering
ssr: {
renderDelay: 3000, // 0 - 15000 (ms)
},
});
In some particular cases, our keyboard shortcuts may conflict with your web app, you can easily disable all our shortcuts by passing a specific property in the JavaScript snippet configuration:
const widget = await markerSDK.loadWidget({
project: '<PROJECT ID>',
// Toggles off all keyboard shortcuts
keyboardShortcuts: false,
});
Need help integrating Marker.io with your web app? We're here to support you! Simply reach out to us through your Marker.io account.
For any bugs, improvements, or feature requests related to this SDK, please contact us via our Support Chat.
Released under the MIT license.
FAQs
Marker.io browser SDK
The npm package @marker.io/browser receives a total of 13,672 weekly downloads. As such, @marker.io/browser popularity was classified as popular.
We found that @marker.io/browser demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 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.