npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

expo-sdk-nestjs

v1.0.3

Published

expo-server-sdk in nestjs

Downloads

34

Readme

build status codecov npm version miniziped size tree shaking MIT licensed

Instalation

$ yarn add expo-sdk-nestjs
$ npm install --save expo-sdk-nestjs

Getting Started

To use Expo-SDK client we need to register module for example in app.module.ts

import { TwilioModule } from 'nestjs-twilio';

@Module({
  imports: [
    ExpoSDKModule.forRoot({
      accessToken: 'xxxx' // accessToken optional
    }),
  ],
})
export class AppModule {}

If you are using the @nestjs/config package from nest, you can use the ConfigModule using the registerAsync() function to inject your environment variables like this in your custom module:

import { Module } from '@nestjs/common';
import { ExpoSDKModule } from 'expo-sdk-nestjs';
import { ConfigModule, ConfigService } from '@nestjs/config';

@Module({
  imports: [
    ExpoSDKModule.forRootAsync({
      imports: [ConfigModule],
      useFactory: (configService: ConfigService) => {
        return {
          accessToken: configService.get('EXPO_PUSH_SECURITY'),
        };
      },
      inject: [ConfigService],
    }),
  ],
  providers: [],
})
export class AppModule {}

Config Options for Module

| Option | Type | | --- | ----------- | | httpAgent | Agent | | maxConcurrentRequests | number | | accessToken | Expo Access Token - string |

Example usage in service.

import { ExpoSDKService } from 'expo-sdk-nestjs';
import { ExpoPushTicket, ExpoPushMessage } from 'expo-server-sdk';

@Injectable()
export class AppService {
  public constructor(private readonly expoService: ExpoSDKService) {}

  async sendNotifications(
    chunks: ExpoPushMessage[][]
  ): Promise<ExpoPushTicket[] | undefined> {
    try {
      const tickets: ExpoPushTicket[] = [];

      for (let i = 0; i < chunks.length; i++) {
        const chunk = chunks[i];
        const ticketChunk =
          await this.expoService.client.sendPushNotificationsAsync(chunk);
        tickets.push(...ticketChunk);
      }
      return tickets;
    } catch (error) {
      this.logger.error(error);
    }
  }
}

For full Client API see EXPO DOCS reference here expo-server-sdk-node repo here

Testing

Example of testing can be found here.

Consider buying me a coffee if you like this project