This is a JavaScript module that can be used to easily include OneSignal code in a website or app that uses Vue for its front-end codebase.
OneSignal is the world's leader for Mobile Push Notifications, Web Push, and In-App Messaging. It is trusted by 2 million+ businesses to send 9 billion Push Notifications per day.
You can find more information on OneSignal here.
Upgrading from Version 1? See our migration guide to get started with v2.
Make sure you install a plugin version compatible with your Vue environment.
Vue | OneSignal Plugin |
---|---|
2 | onesignal-vue |
3 | onesignal-vue3 |
You can use yarn
or npm
.
yarn add @onesignal/onesignal-vue3
npm install --save @onesignal/onesignal-vue3
In Vue 3, you can pass in the OneSignal initialization options directly as an argument to the use
function. You can still initialize separately if you prefer editor benefits like code-completion.
// main
import { createApp } from 'vue'
import OneSignalVuePlugin from '@onesignal/onesignal-vue3'
createApp(App).use(OneSignalVuePlugin, {
appId: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx',
}).mount('#app');
or
//main
import { createApp } from 'vue'
import OneSignalVuePlugin from '@onesignal/onesignal-vue3'
createApp(App).use(OneSignalVuePlugin).mount('#app');
// component
this.$OneSignal.init({
appId: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
});
The OneSignal plugin automatically exposes a $OneSignal
global property accessible inside the application.
You can also leverage Vue's Composition API via the useOneSignal
function that can be called from within setup
.
The init
function returns a promise that resolves when OneSignal is loaded.
Examples
await this.$OneSignal.init({ appId: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' });
// do other stuff
this.$OneSignal.init({ appId: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' }).then(() => {
// do other stuff
});
You can pass other options to the init
function. Use these options to configure personalized prompt options, auto-resubscribe, and more.
If you haven't done so already, you will need to add the OneSignal Service Worker file to your site (learn more).
The OneSignal SDK file must be publicly accessible. You can put them in your top-level root or a subdirectory. However, if you are placing the file not on top-level root make sure to specify the path via the service worker params in the init options (see section above).
Tip:
Visit https://yoursite.com/OneSignalSDKWorker.js
in the address bar to make sure the files are being served successfully.
If IntelliSense is not working as expected in your .vue
file, try adding an import from the OneSignal plugin.
This package includes Typescript support.
interface IOneSignalOneSignal {
Slidedown: IOneSignalSlidedown;
Notifications: IOneSignalNotifications;
Session: IOneSignalSession;
User: IOneSignalUser;
Debug: IOneSignalDebug;
login(externalId: string, jwtToken?: string): Promise<void>;
logout(): Promise<void>;
init(options: IInitObject): Promise<void>;
setConsentGiven(consent: boolean): Promise<void>;
setConsentRequired(requiresConsent: boolean): Promise<void>;
}
See the official OneSignal WebSDK reference for information on all available SDK functions.
Use listeners to react to OneSignal-related events:
Event Name | Callback Argument Type |
---|---|
'click' | NotificationClickEvent |
'foregroundWillDisplay' | NotificationForegroundWillDisplayEvent |
'dismiss' | NotificationDismissEvent |
'permissionChange' | boolean |
'permissionPromptDisplay' | void |
Event Name | Callback Argument Type |
---|---|
'slidedownShown' | boolean |
Event Name | Callback Argument Type |
---|---|
'change' | boolean |
Example
this.$OneSignal.Notifications.addEventListener('change', (event) => {
console.log("The notification was clicked!", event);
});
See the OneSignal WebSDK Reference for all available event listeners.
Contributions, issues and feature requests are welcome!
Feel free to check issues page.
Give a ⭐️ if this project helped you!
Reach out to us via our Discord server!
Copyright © 2023 OneSignal.
This project is Modified MIT licensed.
Enjoy!