Github bot - Unexpected token ; - Glitch

By -

I'm trying to build my own github bot to cherry-pick pull-requests into release branches. There are several examples in Javascript/Typescript and using/not using Probot (Github) available on github:

At the moment I can successfully run my bot locally, but it's not working when deployed to Glitch.

Here's what I did

npx create-probot-app issue_greeter
? App name: issue-greeter
? Description of app: Replies with a greeting when someone opens an issue
? Which template would you like to use? basic-ts => Comment on new issues - written in TypeScript
code issue_greeter

I want this bot to reside under my organization. So while normally you would do the following:

npm start
# Visit http://localhost:3000
> Register Github app
# Visit https://github.com/settings/apps/manifest

I'm doing this manually:

Smee.io - Start new channel

  • Click Start a new channel

    • Webhook Proxy URL = https://smee.io/2TJ4whCGVUpsHdRr
    • Webhook Secret = bJpKnpXCsnhoJYU6O9Z5CEy6eSZ45tdP (random string 1)

  • Now move to the project. Copy .env.example as .env and paste the WEBHOOK_PROXY_URL and WEBHOOK_SECRET

  • Visit the Apps page under your Github Organization (https://github.com/organizations/ORGNAME/settings/apps) and click New GitHub App

New Github app

Here are all other instructions I did (and wrote down while doing them)

But for some reason my Glitch app won't start, and gives the following error:

Glitch app for github bot

There's no WEBHOOK_PROXY_URL, but a WEBHOOK_URL here (as per instructions).

/rbd/pnpm-volume/725725db-f67a-46e6-9310-065c08ff5138/node_modules/.registry.npmjs.org/lru-cache/9.1.2/node_modules/lru-cache/dist/cjs/index.js:27
        onabort;
               ^
SyntaxError: Unexpected token ;
    at Module._compile (internal/modules/cjs/loader.js:723:23)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/rbd/pnpm-volume/725725db-f67a-46e6-9310-065c08ff5138/node_modules/.registry.npmjs.org/@octokit/auth-app/4.0.13/node_modules/@octokit/auth-app/dist-node/index.js:65:24)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)

Note that the generated bundle is already CommonJS

Node on Glitch

What's causing this. I noted somewhere that Glitch seems to be using Node 10, but since everything is locally built that shouldn't be a problem?

Also, is the SMEE-channel still used when deployed to Glitch, or is this only for development?



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk.
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();     TransportClient client = new P
Read more