tejado / telegram-nearby-map Goto Github PK
View Code? Open in Web Editor NEWDiscover the location of nearby Telegram users 📡🌍
License: GNU General Public License v3.0
telegram-nearby-map's People
Stargazers
Watchers
Forkers
robhein 06opotehb dutchosintguy n0isiv mjahanar cybermonitorr pamoy actorexpose m299792458 d3v53c kiku-jw oleiva mukcep 5l1v3r1 runningbard linux-jin zubiden meetgyn guardofparadise caavemaan oshadhavimukthim tracelabs1337 3453-315h korallin cutff streemline vitaliirat evilcry matosdiego alb-310 wh1t3k4t letzgobrandon pabraksas xopodssec1 liutya xenacode-art davidkot dex1234567 haloassassin973 pu55yf3r abdubass 3ill simoejj ir-st supremointra dnoto093 zoutepopcorn adambenaceur sigerello corn123123 takov751 dannythehacker the1976 juanmameza akbarazimifar rmallof randydom marmodsec kunthet hlburgas koji-takahiro irrenriel fishke22 iffixit israelccarvalho serigala1337 8funtik8 mikeyhans nyh770 netishter22 errorincod3 totoro2205 msfgz gautam-rinki himalaya-pamir lexisux rainydays1337 lamsecurity rafterrloggs master88wi bigzero55 sts0mrg0 awwstin17 mrxehmad ethicalsecurity-agency under-web sergeydjam h4xl0r immhopper orinocoz dnshost ukaserge kahluri imanbarati cyber-aesthetic mesizm hulkike-forks t3rmonyx cuangigabyte umarahmad200telegram-nearby-map's Issues
Error at startup
what needs to be done to fix these errors?
Error Cannot GET/ in url 127.0.0.1:3000
help me please,
session opens in mobile app. session name Unknown device nameApp 1.0, TDlib 1.8.2
local site not working =(
what am I doing wrong?
Telegram distance changes
Seems that telegram changed their backend so that the distances are rounded to 500m, 1km, 2km, ... Due to this, the tracking of users is not anymore possible or at lest not anymore accurate. Basically the users are appearing all on one spot.
Can someone confirm my findings? Thanks!
NPM Start error
I am getting the following error:
npm : npm ERR! Missing script: "start"
This occurs when I do npm start after the npm install has completed. Everything in package.json looks fine, so I'm unsure what the issue is.
Auth code
Where do i find the auth code
Need to get rid of CLI auth in favor of UI auth
Hey, I decided to pack your app in Docker, and I achieved it with no problem, but the only thing really annoying me is that CLI authorization to Telegram. Is there the way to make it up from UI?
Here is my Dockerfile to pack it:
FROM node:16.3.0-buster-slim as base
FROM base as builder
RUN apt update
RUN apt install unzip wget -y
RUN mkdir /install
WORKDIR /install
RUN wget https://github.com/tejado/telegram-nearby-map/archive/refs/heads/main.zip
RUN unzip -d /install ./main.zip
FROM base
RUN mkdir /app
WORKDIR /app
COPY --from=builder /install/telegram-nearby-map-main /app
RUN rm package-lock.json
RUN apt update && apt upgrade -y
RUN apt install python3 python3-dev make build-essential -y
RUN npm install
ENTRYPOINT ["npm"]
CMD ["start"]
But I got to start my docker-compose like that:
version: "3"
services:
telegram_maps:
image: map:latest
entrypoint: sleep
command: infinity
volumes:
- ./data/config.js:/app/config.js
ports:
- 3000:3000
restart: always
As you may see, I start with sleep infinity to start the app by hands, authorize and only then I can use it. It would be cool if you could do the UI auth, so anyone can use your tool out of the box with just DOCKER installed.
Error start
i`m ready installed all dependencies in 'npm i' and use npm start then have error
Error: Request failed with status code 500
Send message by chat id
Hello, I can send a message for user only by chat id?
Error: Cannot find module './config.js'
I have problem
Erros in NPM start
I did any correct procedure, but when Start the NPM is giving this error. I already made the installations of the TDLT dependencies
I'm using Debian 11
Even I have a system that uses NPM and it is working properly.
how send Message to them ?
hello !
i cant connect to any body with api
how connect to them with id
i have not username for connection
i need send msg to users find
Showing build failed error!
@parcel/optimizer-terser: You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... }) before using SourceMapConsumer
Problem with login
I have the next problem:
How to solve it?
Segmentation fault: 11 npm run startServer
Hello dear author, could you look at this error,?
I would like to know if your server startup is working
@MacBook-Pro-8 ~/m/telegram-nearby-map (main) [1]> npm start
> start
> npm run buildParcel && npm run startServer
> buildParcel
> parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
✨ Built in 142ms
web-build/index.html 1.55 KB 270ms
web-build/index.a2c0f328.css 8.71 KB 52ms
web-build/index.152cb747.js 386.04 KB 2.57s
> startServer
> node server.js
Current WD: /Users/dvkulikov/map/telegram-nearby-map/lib/tdlib
Lib Path: ./libtdjson.dylib
sh: line 1: 59701 Segmentation fault: 11 npm run startServer
Node & Npm versions
@MacBook-Pro-8 ~/m/telegram-nearby-map (main) [SIGSEGV]> node -v
v19.3.0
@MacBook-Pro-8 ~/m/telegram-nearby-map (main)> npm -v
9.2.0
@MacBook-Pro-8 ~/m/telegram-nearby-map (main)>
How to npm install and start?
why I can't use it
Solved: Parcel SyntaxError: Invalid or unexpected token
Hello,
Using as OS: Almalinux
npm --version
6.14.11
node --version
v10.24.0
npm install
audited 325 packages in 2.11s
78 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
Got the following error when issue: npm start
Any help much appreciated!
TIA
# npm start
> telegram-nearby-map@ start /root/TG/telegram-nearby-map
> npm run buildParcel && npm run startServer
> telegram-nearby-map@ buildParcel /root/TG/telegram-nearby-map
> parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
/root/TG/telegram-nearby-map/node_modules/@parcel/core/lib/Parcel.js:150
#requestTracker
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/root/TG/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/root/TG/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 (/root/TG/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object.<anonymous> (/root/TG/telegram-nearby-map/node_modules/@parcel/core/lib/index.js:81:39)
/root/TG/telegram-nearby-map/node_modules/@parcel/logger/lib/Logger.js:41
#logEmitter
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/root/TG/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/root/TG/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 _logger (/root/TG/telegram-nearby-map/node_modules/parcel/lib/cli.js:54:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! telegram-nearby-map@ buildParcel: `parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the telegram-nearby-map@ buildParcel script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-03-14T08_20_18_489Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! telegram-nearby-map@ start: `npm run buildParcel && npm run startServer`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the telegram-nearby-map@ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-03-14T08_20_18_504Z-debug.log```
Uncaught TypeError: Failed to resolve module specifier "ol/ol.css". Relative references must start with either "/", "./", or "../".
Uncaught TypeError: Failed to resolve module specifier "ol/ol.css". Relative references must start with either "/", "./", or "../".
Which should be the problem?
Getting error when running npm start
start
npm run buildParcel && npm run startServer
buildParcel
parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
error: unknown option `--dist-dir'
npm ERR! code 1
npm ERR! path /home/bro/telegram-nearby-map
npm ERR! command failed
npm ERR! command sh -c parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
npm ERR! A complete log of this run can be found in:
npm ERR! /home/bro/.npm/_logs/2022-11-02T20_38_03_307Z-debug.log
npm ERR! code 1
npm ERR! path /home/bro/telegram-nearby-map
npm ERR! command failed
npm ERR! command sh -c npm run buildParcel && npm run startServer
npm ERR! A complete log of this run can be found in:
npm ERR! /home/bro/.npm/_logs/2022-11-02T20_38_03_360Z-debug.log
--------- the contents of the /home/bro/.npm/_logs/2022-11-02T20_38_03_360Z-debug.log i pasted below
0 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'buildParcel' ]
1 info using [email protected]
2 info using [email protected]
3 timing config:load:defaults Completed in 3ms
4 timing config:load:file:/usr/share/nodejs/npm/npmrc Completed in 3ms
5 timing config:load:builtin Completed in 4ms
6 timing config:load:cli Completed in 3ms
7 timing config:load:env Completed in 1ms
8 timing config:load:file:/home/bro/telegram-nearby-map/.npmrc Completed in 0ms
9 timing config:load:project Completed in 2ms
10 timing config:load:file:/home/bro/.npmrc Completed in 0ms
11 timing config:load:user Completed in 0ms
12 timing config:load:file:/etc/npmrc Completed in 0ms
13 timing config:load:global Completed in 0ms
14 timing config:load:cafile Completed in 1ms
15 timing config:load:validate Completed in 1ms
16 timing config:load:setUserAgent Completed in 1ms
17 timing config:load:setEnvs Completed in 1ms
18 timing config:load Completed in 18ms
19 verbose npm-session 10df51d7e89ee590
20 timing npm:load Completed in 34ms
21 timing command:run-script Completed in 243ms
22 verbose stack Error: command failed
22 verbose stack at ChildProcess. (/usr/share/nodejs/@npmcli/promise-spawn/index.js:64:27)
22 verbose stack at ChildProcess.emit (events.js:314:20)
22 verbose stack at maybeClose (internal/child_process.js:1022:16)
22 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
23 verbose cwd /home/bro/telegram-nearby-map
24 verbose Linux 5.10.0-16-amd64
25 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "buildParcel"
26 verbose node v12.22.12
27 verbose npm v7.5.2
28 error code 1
29 error path /home/bro/telegram-nearby-map
30 error command failed
31 error command sh -c parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
32 verbose exit 1
Error while reading RSA public key
Hi. Great job. When npm start, return message [Error : 0 : Error while reading RSA public key] and after Aborted (core dumped)
TypeError: Cannot read properties of null (reading 'users_nearby')
Hi,
I am not sure if this is an issue on my side/tlg side (since it's a 500 Error) or it a bug (Environment W10) - I get the following error immediately after I hit "Start Search"
TypeError: Cannot read properties of null (reading 'users_nearby')
at TelegramNearby.getNearby (C:\Users\XXXX\Documents\XXXX\telegram-nearby-map-main\lib\telegram-nearby.js:61:39)
06-02-2022 01:09:36 PM - crit: 392078a3-3e0f-405f-9515-b00378920d6e - TypeError: Cannot read properties of null (reading 'users_nearby')
06-02-2022 01:10:12 PM - info: 5e589028-c3cf-41b3-800d-116a01d45524 - POST /getNearby
06-02-2022 01:10:12 PM - info: {"lon":xxx,"lat":xxx}
06-02-2022 01:10:12 PM - warn: undefined
Thanks.
TDLib Error?
Hi! I have just recently tried to run the tool.
The following error was noted in the CLI:
Current WD: d:\Scripts\nodejs\telegram-nearby-map-new\lib\tdlib
Lib Path: tdjson.dll
Listening at http://127.0.0.1:3000
[ 2][t 5][1648985902.399612665][Timer.cpp:67][#1][!Td][&duration > max_duration_] SLOW: [name:change key][duration:2470.9us]
[ 2][t 5][1648985902.399803400][TdDb.cpp:323][#1][!Td] Got PRAGMA user_version = 13
[ 2][t 5][1648985902.403828620][AuthDataShared.cpp:109][#1][!Td] DcId{4} [auth_key_id:1234567890][state:OK][created_at:1641170601.000000]
[ 2][t 5][1648985902.406669616][Session.cpp:167][#1][!SessionProxy:4:main] Generate new session_id 14629334249756723973 for auth key 1234567890 for main DC4
[ 0][t 5][1648985902.775906324][MessagesManager.cpp:5601][#1][!Td] Check have_dialog(dialog_id) failed
It looks to me like the tdlib needs updating. I tried running a fresh install of the latest version of the tool but it kept throwing up lots of different errors.
Can you advise on a fix?
Error: Request failed with status code 500
TypeError: Cannot read properties of null (reading 'users_nearby')
at TelegramNearby.getNearby (C:\PycharmP\Telegram Nearby Map\lib\telegram-nearby.js:54:39)
13-03-2024 11:24:50 AM - crit: f1f42655-9b2f-4434-a99a-00805e5a3b26 - TypeError: Cannot read properties of null (reading 'users_nearby')
× Build failed. @parcel/core: Failed to resolve 'ol/ol.css' from './web-src/web.js'
Hello buddy, i have problem when i run the app.
C:\Program Files\telegram-nearby-map-main>npm start
start
npm run buildParcel && npm run startServer
buildParcel
parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
× Build failed.
@parcel/core: Failed to resolve 'ol/ol.css' from './web-src/web.js'
C:\Program Files\telegram-nearby-map-main\web-src\web.js:1:8
1 | import 'ol/ol.css';
| ^^^^^^^^^^^
2 | import Map from 'ol/Map';
3 | import Overlay from 'ol/Overlay';
Tele
npm error
┌─[✗]─[apashe@apashe]─[~/Desktop/telegram-nearby-map-main]
└──╼ $npm start
start
npm run buildParcel && npm run startServer
buildParcel
parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
🚨 Build failed.
@parcel/optimizer-terser: Unexpected token: punc (()
/home/apashe/Desktop/telegram-nearby-map-main/node_modules/ol/src/proj.js:328:4
327 | */
328 | function (input, opt_output, opt_dimension) {
| ^ Unexpected token: punc (()
329 | const length = input.length;
330 | const dimension = opt_dimension !== undefined ? opt_dimension : 2;
💡 It's likely that Terser doesn't support this syntax yet.
npm ERR! code 1
npm ERR! path /home/apashe/Desktop/telegram-nearby-map-main
npm ERR! command failed
npm ERR! command sh -c parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
npm ERR! A complete log of this run can be found in:
npm ERR! /home/apashe/.npm/_logs/2022-03-24T23_01_47_824Z-debug.log
npm ERR! code 1
npm ERR! path /home/apashe/Desktop/telegram-nearby-map-main
npm ERR! command failed
npm ERR! command sh -c npm run buildParcel && npm run startServer
npm ERR! A complete log of this run can be found in:
npm ERR! /home/apashe/.npm/_logs/2022-03-24T23_01_47_839Z-debug.log
NPM bugs with tdlib
Hello, trying to start app from linux and linux, made npm install, configureg config.js and getting errors:
LINUX:
npm run buildParcel && npm run startServer
> telegram-nearby-map@ buildParcel /home/supadm/web/telegram-nearby-map
> parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
/home/supadm/web/telegram-nearby-map/node_modules/@parcel/core/lib/Parcel.js:149
#requestTracker
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/home/supadm/web/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/home/supadm/web/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 (/home/supadm/web/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object.<anonymous> (/home/supadm/web/telegram-nearby-map/node_modules/@parcel/core/lib/index.js:81:39)
/home/supadm/web/telegram-nearby-map/node_modules/@parcel/logger/lib/Logger.js:41
#logEmitter
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/home/supadm/web/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/home/supadm/web/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 _logger (/home/supadm/web/telegram-nearby-map/node_modules/parcel/lib/cli.js:54:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! telegram-nearby-map@ buildParcel: `parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the telegram-nearby-map@ buildParcel script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/supadm/.npm/_logs/2021-11-18T15_06_52_552Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! telegram-nearby-map@ start: `npm run buildParcel && npm run startServer`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the telegram-nearby-map@ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/supadm/.npm/_logs/2021-11-18T15_06_52_577Z-debug.log
I can send log file if it's needed
MACOS:
/Users/macbook/tools/telegram-nearby-map/node_modules/tdl-tdlib-addon/dist/index.js:37
this._addon.load_tdjson(libraryFile);
^
Error: Dynamic Loading Error: dlopen(./libtdjson.so, 0x0005): tried: './libtdjson.so' (not a mach-o file), '/usr/local/lib/libtdjson.so' (not a mach-o file), '/usr/lib/libtdjson.so' (no such file), '/Users/macbook/tools/telegram-nearby-map/lib/tdlib/libtdjson.so' (not a mach-o file), '/usr/local/lib/libtdjson.so' (not a mach-o file), '/usr/lib/libtdjson.so' (no such file)
at new TDLib (/Users/macbook/tools/telegram-nearby-map/node_modules/tdl-tdlib-addon/dist/index.js:37:17)
Installed tdlib via brew and copyed binary files to /usr/local/lib/ from https://github.com/Bannerets/tdlib-binaries/tree/master/1.2.0/macos and linux but it steel doesn't worked(
It would be greate if you can create a docker image or help with bugfixing on one of platforms
Waiting for reply ;)
failed to resolve 'ol/ol.css' from './web-src/web.js'
hello, i have this problem:
start
npm run buildParcel && npm run startServer
buildParcel
parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
× Build failed.
@parcel/core: Failed to resolve 'ol/ol.css' from './web-src/web.js'
C:\Users\MYUSERPRIVATEXD(changed now)\Downloads\telegram-nearby-map-main\telegram-nearby-map-main\web-src\web.js:1:8
1 | import 'ol/ol.css';
| ^^^^^^^^^^^
2 | import Map from 'ol/Map';
3 | import Overlay from 'ol/Overlay';
Another npm start issue
Vanilla Ubuntu 20.04 srv full patched here. Stuck on trying to start as other users, with a different problem.
Node v10.19.0
npm 6.14.4
> npm run buildParcel && npm run startServer
> telegram-nearby-map@ buildParcel /opt/telegram-nearby-map
> parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
/opt/telegram-nearby-map/node_modules/@parcel/core/lib/Parcel.js:149
#requestTracker
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/opt/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/opt/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 (/opt/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object.<anonymous> (/opt/telegram-nearby-map/node_modules/@parcel/core/lib/index.js:81:39)
/opt/telegram-nearby-map/node_modules/@parcel/logger/lib/Logger.js:41
#logEmitter
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/opt/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/opt/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 _logger (/opt/telegram-nearby-map/node_modules/parcel/lib/cli.js:54:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! telegram-nearby-map@ buildParcel: `parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the telegram-nearby-map@ buildParcel script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-02-08T07_42_41_772Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! telegram-nearby-map@ start: `npm run buildParcel && npm run startServer`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the telegram-nearby-map@ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-02-08T07_42_41_780Z-debug.log
Any idea on how to fix?
Thanks
Cant Open db.sqlite f
hello sir thanks for sharing this great script but i have a problem when i want to open db.sqlite file witch suppose to find User ID and Location in , it says its not database file , i tried sqlite browser
Thanks a lot
Incompatible with MacOS?
I'm running the program, but the output says Error: Dynamic Loading Error: dlopen(./libtdjson.dylib, 0x0005): Library not loaded: /usr/local/opt/[email protected]/lib/libssl.1.1.dylib
and then says errors like "no such file" "no such file, not in dyld cache"
if can't, can i just delete the folder to clear the dependencies?
Error: Request failed with status code 500
Error: Request failed with status code 500
Database dosenot opem
hello man could you tell us how can we open the database ?
2 Errors
Hi :-)
I get this errors while launching the app :
-
node:55470) UnhandledPromiseRejectionWarning: #
-
TypeError: Cannot read property 'users_nearby' of null
Can someone help me please ?
Possibility to output User ID and Lat Lng?
Hi there! I absolutely love this tool and I have been showcasing it during various OSINT demos.
Is there a possibility to output the User ID and their associated geolocations, perhaps to a CSV? The reason I'm asking is because I think having this data and then using a third party application to triangulate users that appear across multiple locations would be hugely beneficial. I have tried implementing a few tweaks to the script to see if I can do it myself, but I have had no luck.
Again, fantastic work with this utility! It is fantastic!
Handshake is not yet ready
Listening at http://127.0.0.1:3000
[ 2][t 5][1629098971.683029174][Timer.cpp:67][#1][!Td][&duration > max_duration_] SLOW: [name:change key][duration:5154.9us]
[ 2][t 5][1629098971.683246850][TdDb.cpp:323][#1][!Td] Got PRAGMA user_version = 13
[ 2][t 5][1629098971.686511278][AuthDataShared.cpp:109][#1][!Td] DcId{1} [auth_key_id:0][state:Empty][created_at:0.000000]
[ 2][t 5][1629098971.687593221][Session.cpp:167][#1][!SessionProxy:1:main] Generate new session_id 466704***********286006 for auth key 0 for main DC1
Please enter phone number: [ 2][t 3][1629098973.598073482][Session.cpp:1274][#1][!Session:1:main::HandshakeActor] Failed to open connection: [Error : 10054 : Error on [fd:00000000000003FC] : [149.154.175.50:443] to DcId{1} from [0.0.0.0:51632]]
[ 2][t 5][1629098973.598258018][Session.cpp:1207][#1][!Session:1:main] Handshake is not yet ready
How to avoind result mixing/caching?
Hello,
I just wonder is here any configurable options to ignore || to clean up previous results?. (
I mean; for example if i search location A and then location B then the location A's results mixed with B's result.)
TIA
Dc
1
success in npm start, but can't load maps
success in npm start, but can't load maps.. cant you solve it?
https://tele-map-solo.herokuapp.com/
in heroku console, there is message "Please enter phone number:" but i can't input phone number
Doesnt work: SyntaxError
Hello. Trying to start, but i get syntax error for both npm ci and npm install.
/home/ubuntu/repos/telegram-nearby-map/node_modules/@parcel/core/lib/Parcel.js:149
#requestTracker
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object.<anonymous> (/home/ubuntu/repos/telegram-nearby-map/node_modules/@parcel/core/lib/index.js:81:39)
/home/ubuntu/repos/telegram-nearby-map/node_modules/@parcel/logger/lib/Logger.js:41
#logEmitter
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 _logger (/home/ubuntu/repos/telegram-nearby-map/node_modules/parcel/lib/cli.js:54:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! telegram-nearby-map@ buildParcel: `parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the telegram-nearby-map@ buildParcel script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Full output:
ubuntu@test-container:~/repos/telegram-nearby-map$ git config --get remote.origin.url
https://github.com/tejado/telegram-nearby-map.git
ubuntu@test-container:~/repos/telegram-nearby-map$ LANG=en_US.UTF-8 git checkout main && git pull
M package-lock.json
Already on 'main'
Your branch is up to date with 'origin/main'.
Уже обновлено.
ubuntu@test-container:~/repos/telegram-nearby-map$ LC_ALL=en_US.UTF-8 npm ci
npm WARN prepare removing existing node_modules/ before installation
> [email protected] install /home/ubuntu/repos/telegram-nearby-map/node_modules/tdl-tdlib-addon
> node-gyp rebuild
make: Entering directory '/home/ubuntu/repos/telegram-nearby-map/node_modules/tdl-tdlib-addon/build'
CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
AR(target) Release/obj.target/../node-addon-api/nothing.a
COPY Release/nothing.a
CXX(target) Release/obj.target/td/td.o
SOLINK_MODULE(target) Release/obj.target/td.node
COPY Release/td.node
make: Leaving directory '/home/ubuntu/repos/telegram-nearby-map/node_modules/tdl-tdlib-addon/build'
> [email protected] install /home/ubuntu/repos/telegram-nearby-map/node_modules/msgpackr-extract
> node-gyp-build
make: Entering directory '/home/ubuntu/repos/telegram-nearby-map/node_modules/msgpackr-extract/build'
CXX(target) Release/obj.target/msgpackr-extract/src/extract.o
../src/extract.cpp: In member function ‘v8::Local<v8::Value> Extractor::extractStrings(int, int, uint8_t*)’:
../src/extract.cpp:161:36: warning: ignoring return value of ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’, declared with attribute warn_unused_result [-Wunused-result]
161 | array->Set(context, i, target[i]);
| ^
In file included from ../src/extract.cpp:8:
/usr/include/nodejs/deps/v8/include/v8.h:3252:37: note: declared here
3252 | V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
| ^~~
In file included from ../src/extract.cpp:9:
../src/extract.cpp: At global scope:
/usr/include/nodejs/src/node.h:593:51: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_context_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, v8::Local<v8::Context>, void*)’} [-Wcast-function-type]
593 | (node::addon_context_register_func) (regfunc), \
| ^
/usr/include/nodejs/src/node.h:611:3: note: in expansion of macro ‘NODE_MODULE_CONTEXT_AWARE_X’
611 | NODE_MODULE_CONTEXT_AWARE_X(modname, regfunc, NULL, 0)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/extract.cpp:269:1: note: in expansion of macro ‘NODE_MODULE_CONTEXT_AWARE’
269 | NODE_MODULE_CONTEXT_AWARE(extractor, initializeModule);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ../src/extract.cpp:8:
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
/usr/include/nodejs/src/node_object_wrap.h:84:78: required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
9502 | reinterpret_cast<Callback>(callback), type);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
../../nan/nan_object_wrap.h:65:61: required from here
/usr/include/nodejs/deps/v8/include/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
SOLINK_MODULE(target) Release/obj.target/msgpackr-extract.node
COPY Release/msgpackr-extract.node
make: Leaving directory '/home/ubuntu/repos/telegram-nearby-map/node_modules/msgpackr-extract/build'
> [email protected] install /home/ubuntu/repos/telegram-nearby-map/node_modules/lmdb-store
> node-gyp-build
make: Entering directory '/home/ubuntu/repos/telegram-nearby-map/node_modules/lmdb-store/build'
CXX(target) Release/obj.target/lmdb/src/node-lmdb.o
CC(target) Release/obj.target/lmdb/dependencies/lmdb/libraries/liblmdb/midl.o
CC(target) Release/obj.target/lmdb/dependencies/lmdb/libraries/liblmdb/chacha8.o
CC(target) Release/obj.target/lmdb/dependencies/lz4/lib/lz4.o
CXX(target) Release/obj.target/lmdb/src/env.o
../src/env.cpp: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE EnvWrap::open(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/env.cpp:559:55: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Local<v8::Value>)’ is deprecated: Use Isolate version [-Wdeprecated-declarations]
559 | rc = mdb_env_open(ew->env, *String::Utf8Value(path), flags, 0664);
| ^
In file included from /usr/include/nodejs/deps/v8/include/v8.h:26,
from ../src/node-lmdb.h:29,
from ../src/env.cpp:25:
/usr/include/nodejs/deps/v8/include/v8.h:2892:28: note: declared here
2892 | explicit Utf8Value(Local<v8::Value> obj));
| ^~~~~~~~~
/usr/include/nodejs/deps/v8/include/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
324 | declarator __attribute__((deprecated(message)))
| ^~~~~~~~~~
CXX(target) Release/obj.target/lmdb/src/compression.o
CXX(target) Release/obj.target/lmdb/src/ordered-binary.o
../src/ordered-binary.cpp: In function ‘size_t valueToKey(const v8::Local<v8::Value>&, uint8_t*, size_t, bool, bool)’:
../src/ordered-binary.cpp:68:18: warning: ‘number’ may be used uninitialized in this function [-Wmaybe-uninitialized]
68 | uint64_t asInt = *((uint64_t*) &number);
| ^~~~~
CXX(target) Release/obj.target/lmdb/src/misc.o
CXX(target) Release/obj.target/lmdb/src/txn.o
CXX(target) Release/obj.target/lmdb/src/dbi.o
../src/dbi.cpp: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE DbiWrap::ctor(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/dbi.cpp:171:74: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Local<v8::Value>)’ is deprecated: Use Isolate version [-Wdeprecated-declarations]
171 | rc = mdb_dbi_open(txn, nameIsNull ? nullptr : *String::Utf8Value(name), flags, &dbi);
| ^
In file included from /usr/include/nodejs/deps/v8/include/v8.h:26,
from ../src/node-lmdb.h:29,
from ../src/dbi.cpp:25:
/usr/include/nodejs/deps/v8/include/v8.h:2892:28: note: declared here
2892 | explicit Utf8Value(Local<v8::Value> obj));
| ^~~~~~~~~
/usr/include/nodejs/deps/v8/include/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
324 | declarator __attribute__((deprecated(message)))
| ^~~~~~~~~~
CXX(target) Release/obj.target/lmdb/src/cursor.o
CC(target) Release/obj.target/lmdb/dependencies/lmdb/libraries/liblmdb/mdb.o
SOLINK_MODULE(target) Release/obj.target/lmdb.node
COPY Release/lmdb.node
make: Leaving directory '/home/ubuntu/repos/telegram-nearby-map/node_modules/lmdb-store/build'
> @parcel/[email protected] install /home/ubuntu/repos/telegram-nearby-map/node_modules/@parcel/watcher
> node-gyp-build
> [email protected] postinstall /home/ubuntu/repos/telegram-nearby-map/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js:
> https://opencollective.com/core-js
> https://patreon.com/zloirock
> https://paypal.me/zloirock
> bitcoin: bc1qlea7544qtsmj2rayg0lthvza9fau63ux0fstcz
Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
added 769 packages in 20.561s
ubuntu@test-container:~/repos/telegram-nearby-map$ npm start
> telegram-nearby-map@ start /home/ubuntu/repos/telegram-nearby-map
> npm run buildParcel && npm run startServer
> telegram-nearby-map@ buildParcel /home/ubuntu/repos/telegram-nearby-map
> parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
/home/ubuntu/repos/telegram-nearby-map/node_modules/@parcel/core/lib/Parcel.js:149
#requestTracker
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object.<anonymous> (/home/ubuntu/repos/telegram-nearby-map/node_modules/@parcel/core/lib/index.js:81:39)
/home/ubuntu/repos/telegram-nearby-map/node_modules/@parcel/logger/lib/Logger.js:41
#logEmitter
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 _logger (/home/ubuntu/repos/telegram-nearby-map/node_modules/parcel/lib/cli.js:54:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! telegram-nearby-map@ buildParcel: `parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the telegram-nearby-map@ buildParcel script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/ubuntu/.npm/_logs/2021-11-14T18_06_23_130Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! telegram-nearby-map@ start: `npm run buildParcel && npm run startServer`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the telegram-nearby-map@ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/ubuntu/.npm/_logs/2021-11-14T18_06_23_145Z-debug.log
ubuntu@test-container:~/repos/telegram-nearby-map$ cat /home/ubuntu/.npm/_logs/2021-11-14T18_06_23_130Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'buildParcel' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prebuildParcel', 'buildParcel', 'postbuildParcel' ]
5 info lifecycle telegram-nearby-map@~prebuildParcel: telegram-nearby-map@
6 info lifecycle telegram-nearby-map@~buildParcel: telegram-nearby-map@
7 verbose lifecycle telegram-nearby-map@~buildParcel: unsafe-perm in lifecycle true
8 verbose lifecycle telegram-nearby-map@~buildParcel: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/ubuntu/repos/telegram-nearby-map/node_modules/.bin:/usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/ubuntu/repos/telegram-nearby-map/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle telegram-nearby-map@~buildParcel: CWD: /home/ubuntu/repos/telegram-nearby-map
10 silly lifecycle telegram-nearby-map@~buildParcel: Args: [ '-c',
10 silly lifecycle 'parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/' ]
11 silly lifecycle telegram-nearby-map@~buildParcel: Returned: code: 1 signal: null
12 info lifecycle telegram-nearby-map@~buildParcel: Failed to exec buildParcel script
13 verbose stack Error: telegram-nearby-map@ buildParcel: `parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid telegram-nearby-map@
15 verbose cwd /home/ubuntu/repos/telegram-nearby-map
16 verbose Linux 5.4.0-90-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "buildParcel"
18 verbose node v10.19.0
19 verbose npm v6.14.4
20 error code ELIFECYCLE
21 error errno 1
22 error telegram-nearby-map@ buildParcel: `parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/`
22 error Exit status 1
23 error Failed at the telegram-nearby-map@ buildParcel script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
ubuntu@test-container:~/repos/telegram-nearby-map$ cat /home/ubuntu/.npm/_logs/2021-11-14T18_06_23_145Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle telegram-nearby-map@~prestart: telegram-nearby-map@
6 info lifecycle telegram-nearby-map@~start: telegram-nearby-map@
7 verbose lifecycle telegram-nearby-map@~start: unsafe-perm in lifecycle true
8 verbose lifecycle telegram-nearby-map@~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/ubuntu/repos/telegram-nearby-map/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle telegram-nearby-map@~start: CWD: /home/ubuntu/repos/telegram-nearby-map
10 silly lifecycle telegram-nearby-map@~start: Args: [ '-c', 'npm run buildParcel && npm run startServer' ]
11 silly lifecycle telegram-nearby-map@~start: Returned: code: 1 signal: null
12 info lifecycle telegram-nearby-map@~start: Failed to exec start script
13 verbose stack Error: telegram-nearby-map@ start: `npm run buildParcel && npm run startServer`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid telegram-nearby-map@
15 verbose cwd /home/ubuntu/repos/telegram-nearby-map
16 verbose Linux 5.4.0-90-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v10.19.0
19 verbose npm v6.14.4
20 error code ELIFECYCLE
21 error errno 1
22 error telegram-nearby-map@ start: `npm run buildParcel && npm run startServer`
22 error Exit status 1
23 error Failed at the telegram-nearby-map@ start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
ubuntu@test-container:~/repos/telegram-nearby-map$ npm install
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
audited 769 packages in 2.551s
145 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
ubuntu@test-container:~/repos/telegram-nearby-map$ npm start
> telegram-nearby-map@ start /home/ubuntu/repos/telegram-nearby-map
> npm run buildParcel && npm run startServer
> telegram-nearby-map@ buildParcel /home/ubuntu/repos/telegram-nearby-map
> parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/
/home/ubuntu/repos/telegram-nearby-map/node_modules/@parcel/core/lib/Parcel.js:149
#requestTracker
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object.<anonymous> (/home/ubuntu/repos/telegram-nearby-map/node_modules/@parcel/core/lib/index.js:81:39)
/home/ubuntu/repos/telegram-nearby-map/node_modules/@parcel/logger/lib/Logger.js:41
#logEmitter
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:83:7)
at NativeCompileCache._moduleCompile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:240:18)
at Module._compile (/home/ubuntu/repos/telegram-nearby-map/node_modules/v8-compile-cache/v8-compile-cache.js:184:36)
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 _logger (/home/ubuntu/repos/telegram-nearby-map/node_modules/parcel/lib/cli.js:54:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! telegram-nearby-map@ buildParcel: `parcel build ./web-src/index.html --public-url / --dist-dir ./web-build/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the telegram-nearby-map@ buildParcel script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/ubuntu/.npm/_logs/2021-11-14T18_09_43_654Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! telegram-nearby-map@ start: `npm run buildParcel && npm run startServer`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the telegram-nearby-map@ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/ubuntu/.npm/_logs/2021-11-14T18_09_43_669Z-debug.log
ubuntu@test-container:~/repos/telegram-nearby-map$ cat config.js
var config = {}
// your telegram API credentials
// please go to https://my.telegram.org to create your API credentials
config.telegramApiId = '********';
config.telegramApiHash = '********************************';
// server settings
config.hostname = '127.0.0.1';
config.port = 3000;
module.exports = config;
ids
Hello. Is it possible to find out the id of telegram users?
Can you add a function to show usernames of accounts so can message them
Hello, when I execute npm start, there is a problem on the picture.
Mac ?
Hi
Is this program only works with Linux ?
Problem to use (or so I think)
Hello friends, I get a message when doing the steps of the "readme" and do not know if it is a situation of my pc or the repo, if you can help me, I would appreciate it :)
I get the following:
proxy
Hello,
Is it possible to set proxy ?
Best Regards
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.