Getting Error on Heroku Failed to launch chrome - node.js

I'm using Puppeteer on Heroku and I receive the following error:
2022-10-03T16:51:52.616196+00:00 app[web.1]: Error: Failed to launch the browser process!
2022-10-03T16:51:52.616214+00:00 app[web.1]: [1003/165152.260124:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
2022-10-03T16:51:52.616214+00:00 app[web.1]: #0 0x55894fa52339 base::debug::CollectStackTrace()
2022-10-03T16:51:52.616215+00:00 app[web.1]: #1 0x55894f9c8f23 base::debug::StackTrace::StackTrace()
2022-10-03T16:51:52.616215+00:00 app[web.1]: #2 0x55894f9c6070 logging::LogMessage::~LogMessage()
2022-10-03T16:51:52.616215+00:00 app[web.1]: #3 0x55894d9c6c2b content::ZygoteHostImpl::Init()
2022-10-03T16:51:52.616216+00:00 app[web.1]: #4 0x55894f543c0f content::ContentMainRunnerImpl::Initialize()
2022-10-03T16:51:52.616216+00:00 app[web.1]: #5 0x55894f541bfd content::RunContentProcess()
2022-10-03T16:51:52.616216+00:00 app[web.1]: #6 0x55894f541d4e content::ContentMain()
2022-10-03T16:51:52.616217+00:00 app[web.1]: #7 0x55894f59920a headless::(anonymous namespace)::RunContentMain()
2022-10-03T16:51:52.616218+00:00 app[web.1]: #8 0x55894f598f15 headless::HeadlessShellMain()
2022-10-03T16:51:52.616219+00:00 app[web.1]: #9 0x55894be7a1e3 ChromeMain
2022-10-03T16:51:52.616219+00:00 app[web.1]: #10 0x7f8e87025d90 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x29d8f)
2022-10-03T16:51:52.616219+00:00 app[web.1]: #11 0x7f8e87025e40 __libc_start_main
2022-10-03T16:51:52.616220+00:00 app[web.1]: #12 0x55894be7a02a _start
2022-10-03T16:51:52.616221+00:00 app[web.1]:
2022-10-03T16:51:52.616222+00:00 app[web.1]:
2022-10-03T16:51:52.616222+00:00 app[web.1]:
2022-10-03T16:51:52.616222+00:00 app[web.1]: TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
2022-10-03T16:51:52.616223+00:00 app[web.1]:
2022-10-03T16:51:52.616223+00:00 app[web.1]: at onClose (/app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:286:20)
2022-10-03T16:51:52.616224+00:00 app[web.1]: at Interface.<anonymous> (/app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:274:24)
2022-10-03T16:51:52.616224+00:00 app[web.1]: at Interface.emit (node:events:525:35)
2022-10-03T16:51:52.616225+00:00 app[web.1]: at Interface.close (node:readline:590:8)
2022-10-03T16:51:52.616225+00:00 app[web.1]: at Socket.onend (node:readline:280:10)
2022-10-03T16:51:52.616225+00:00 app[web.1]: at Socket.emit (node:events:525:35)
2022-10-03T16:51:52.616226+00:00 app[web.1]: at endReadableNT (node:internal/streams/readable:1358:12)
2022-10-03T16:51:52.616226+00:00 app[web.1]: at processTicksAndRejections (node:internal/process/task_queues:83:21)
My Code:
const browser = await puppeteer.launch({
args: ["--no-sandbox", "--disable-setuid-sandbox"],
});
puppeteer heroku buildpack installed !
I tried some solutions but I was not successful.

Related

Parse-Server on Heroku

I am trying to set up Parse-Server on Heroku along with MongoDB, starting from the classic https://github.com/parse-community/parse-server-example.git.
After going up to a certain point I hit this problem where I can see the following in the logs:
... app[web.1]: MongoServerError: user is not allowed to do action [find] on [test._SCHEMA]
... app[web.1]: at MessageStream.messageHandler (/app/node_modules/parse-server/node_modules/mongodb/lib/cmap/connection.js:462:30)
... app[web.1]: at MessageStream.emit (node:events:513:28)
... app[web.1]: at processIncomingData (/app/node_modules/parse-server/node_modules/mongodb/lib/cmap/message_stream.js:108:16)
... app[web.1]: at MessageStream._write (/app/node_modules/parse-server/node_modules/mongodb/lib/cmap/message_stream.js:28:9)
... app[web.1]: at writeOrBuffer (node:internal/streams/writable:392:12)
... app[web.1]: at _write (node:internal/streams/writable:333:10)
... app[web.1]: at Writable.write (node:internal/streams/writable:337:10)
... app[web.1]: at TLSSocket.ondata (node:internal/streams/readable:766:22)
... app[web.1]: at TLSSocket.emit (node:events:513:28)
... app[web.1]: at addChunk (node:internal/streams/readable:324:12) {
... app[web.1]: ok: 0,
... app[web.1]: code: 8000,
... app[web.1]: codeName: 'AtlasError'
Why do I get this .... user is not allowed to do action [find] on [test._SCHEMA]
Any idea of how to deal with this problem ?

MODULE not found error with nodeJs app on heroku

I am trying to deploy my project on heroku but receiving module not found error.It took my 3 days and I still do not know the exact reason.Please help me.
2022-06-10T14:24:19.535051+00:00 app[web.1]: requireStack: [
2022-06-10T14:24:19.535051+00:00 app[web.1]: '/app/node_modules/mongoose/lib/helpers/cursor/eachAsync.js',
2022-06-10T14:24:19.535051+00:00 app[web.1]: '/app/node_modules/mongoose/lib/cursor/QueryCursor.js',
2022-06-10T14:24:19.535052+00:00 app[web.1]: '/app/node_modules/mongoose/lib/query.js',
2022-06-10T14:24:19.535052+00:00 app[web.1]: '/app/node_modules/mongoose/lib/index.js',
2022-06-10T14:24:19.535052+00:00 app[web.1]: '/app/node_modules/mongoose/index.js',
2022-06-10T14:24:19.535052+00:00 app[web.1]: '/app/server.js'
2022-06-10T14:24:19.535052+00:00 app[web.1]: ]
2022-06-10T14:24:19.535053+00:00 app[web.1]: }
2022-06-10T14:24:19.535057+00:00 app[web.1]:
2022-06-10T14:24:19.535057+00:00 app[web.1]: Node.js v18.3.0
2022-06-10T14:24:19.727936+00:00 heroku[web.1]: Process exited with status 1
2022-06-10T14:24:19.798623+00:00 heroku[web.1]: State changed from starting to crashed
2022-06-10T15:00:50.000000+00:00 app[api]: Build started by user bakhtiyorjondadajonov#gmail.com
2022-06-10T15:01:37.186809+00:00 heroku[web.1]: State changed from crashed to starting
2022-06-10T15:01:43.232647+00:00 heroku[web.1]: Starting process with command `npm start`
2022-06-10T15:01:45.131815+00:00 app[web.1]:
2022-06-10T15:01:45.131826+00:00 app[web.1]: > starter-natours#1.0.0 start
2022-06-10T15:01:45.131826+00:00 app[web.1]: > node server.js
2022-06-10T15:01:45.131827+00:00 app[web.1]:
2022-06-10T15:01:45.362540+00:00 app[web.1]: node:internal/modules/cjs/loader:942
2022-06-10T15:01:45.362541+00:00 app[web.1]: throw err;
2022-06-10T15:01:45.362542+00:00 app[web.1]: ^
2022-06-10T15:01:45.362542+00:00 app[web.1]:
2022-06-10T15:01:45.362542+00:00 app[web.1]: Error: Cannot find module '../../error/eachAsyncMultiError'
2022-06-10T15:01:45.362543+00:00 app[web.1]: Require stack:
2022-06-10T15:01:45.362543+00:00 app[web.1]: - /app/node_modules/mongoose/lib/helpers/cursor/eachAsync.js
2022-06-10T15:01:45.362543+00:00 app[web.1]: - /app/node_modules/mongoose/lib/cursor/QueryCursor.js
2022-06-10T15:01:45.362544+00:00 app[web.1]: - /app/node_modules/mongoose/lib/query.js
2022-06-10T15:01:45.362544+00:00 app[web.1]: - /app/node_modules/mongoose/lib/index.js
2022-06-10T15:01:45.362544+00:00 app[web.1]: - /app/node_modules/mongoose/index.js
2022-06-10T15:01:45.362545+00:00 app[web.1]: - /app/server.js

Laravel 8 and JetStream npm run dev error in windows

npm run dev
cmd error
[enter image description henter image description hereere]2
node:events:498
throw er; // Unhandled 'error' event
^
Error: write EIO
at afterWriteDispatched (node:internal/stream_base_commons:160:15)
at writeGeneric (node:internal/stream_base_commons:151:3)
at WriteStream.Socket._writeGeneric (node:net:795:11)
at WriteStream.Socket._write (node:net:807:8)
at writeOrBuffer (node:internal/streams/writable:389:12)
at _write (node:internal/streams/writable:330:10)
at WriteStream.Writable.write (node:internal/streams/writable:334:10)
at LogUpdate.write (C:\wamp64\www\hospital_app\node_modules\webpackbar\dist\index.cjs:1384:35)
at LogUpdate.render (C:\wamp64\www\hospital_app\node_modules\webpackbar\dist\index.cjs:1374:10)
at FancyReporter._renderStates (C:\wamp64\www\hospital_app\node_modules\webpackbar\dist\index.cjs:1456:15)
Emitted 'error' event on WriteStream instance at:
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -4070,
code: 'EIO',
syscall: 'write'
node and npm version are
C:\wamp64\www\hospital_app>node -v
v16.14.0
C:\wamp64\www\hospital_app>npm -v
8.3.1
pls help me to solve this ?

Is there a way to cancel an awaiting POST request in a Node.js environment?

Right now, my client application has a button that sends a POST request when it is clicked. The request is sent to a server that I've deployed on Heroku that has a Postgres database. When I click the button once, it takes ~3-4 seconds for the request to be fully processed as the function has a lot of awaits in it. When I click the button very fast however, I end up getting a bunch of the following:
2021-05-13T15:49:53.801769+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=POST path="/featuresNearMe" host=sparrow-testing.herokuapp.com request_id=b03523d9-acb0-4140-832f-7af56fbeee4c fwd="143.229.250.40" dyno=web.1 connect=0ms service=30000ms status=503 bytes=0 protocol=https
2021-05-13T15:49:54.230124+00:00 app[web.1]: TimeoutError: Navigation timeout of 30000 ms exceeded
2021-05-13T15:49:54.230126+00:00 app[web.1]: at /app/node_modules/puppeteer/lib/cjs/puppeteer/common/LifecycleWatcher.js:106:111
2021-05-13T15:49:54.242812+00:00 app[web.1]: (node:21) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [process]. Use emitter.setMaxListeners() to increase limit
2021-05-13T15:49:54.242813+00:00 app[web.1]: (Use `node --trace-warnings ...` to show where the warning was created)
2021-05-13T15:49:54.242879+00:00 app[web.1]: (node:21) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added to [process]. Use emitter.setMaxListeners() to increase limit
2021-05-13T15:49:54.242920+00:00 app[web.1]: (node:21) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGTERM listeners added to [process]. Use emitter.setMaxListeners() to increase limit
2021-05-13T15:49:54.242952+00:00 app[web.1]: (node:21) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGHUP listeners added to [process]. Use emitter.setMaxListeners() to increase limit
My Puppeteer awaits also throw an error:
2021-05-13T15:49:54.942751+00:00 app[web.1]: Error: Failed to launch the browser process!
2021-05-13T15:49:54.942752+00:00 app[web.1]: [0513/154954.311863:ERROR:platform_thread_posix.cc(135)] pthread_create: Resource temporarily unavailable (11)
2021-05-13T15:49:54.942753+00:00 app[web.1]: [0513/154954.311951:FATAL:memory_dump_manager.cc(282)] Check failed: started.
2021-05-13T15:49:54.942753+00:00 app[web.1]: #0 0x564866efa259 base::debug::CollectStackTrace()
2021-05-13T15:49:54.942754+00:00 app[web.1]: #1 0x564866e669e3 base::debug::StackTrace::StackTrace()
2021-05-13T15:49:54.942754+00:00 app[web.1]: #2 0x564866e77610 logging::LogMessage::~LogMessage()
2021-05-13T15:49:54.942754+00:00 app[web.1]: #3 0x564866e780ce logging::LogMessage::~LogMessage()
2021-05-13T15:49:54.942755+00:00 app[web.1]: #4 0x564866f2dde3 base::trace_event::MemoryDumpManager::GetOrCreateBgTaskRunnerLocked()
2021-05-13T15:49:54.942755+00:00 app[web.1]: #5 0x564866f2dd32 base::trace_event::MemoryDumpManager::GetDumpThreadTaskRunner()
2021-05-13T15:49:54.942755+00:00 app[web.1]: #6 0x5648654cdf31 content::InitializeBrowserMemoryInstrumentationClient()
2021-05-13T15:49:54.942756+00:00 app[web.1]: #7 0x564866e06fce content::ContentMainRunnerImpl::RunBrowser()
2021-05-13T15:49:54.942756+00:00 app[web.1]: #8 0x564866e06c5d content::ContentMainRunnerImpl::Run()
2021-05-13T15:49:54.942756+00:00 app[web.1]: #9 0x564866e0429d content::RunContentProcess()
2021-05-13T15:49:54.942757+00:00 app[web.1]: #10 0x564866e04c3d content::ContentMain()
2021-05-13T15:49:54.942757+00:00 app[web.1]: #11 0x564866e60c29 headless::HeadlessBrowserMain()
2021-05-13T15:49:54.942757+00:00 app[web.1]: #12 0x564866e6093a headless::HeadlessShellMain()
2021-05-13T15:49:54.942757+00:00 app[web.1]: #13 0x564863e913e1 ChromeMain
2021-05-13T15:49:54.942758+00:00 app[web.1]: #14 0x7fcf7d9460b3 __libc_start_main
2021-05-13T15:49:54.942758+00:00 app[web.1]: #15 0x564863e9122a _start
2021-05-13T15:49:54.942758+00:00 app[web.1]:
2021-05-13T15:49:54.942758+00:00 app[web.1]: Received signal 6
2021-05-13T15:49:54.942759+00:00 app[web.1]: #0 0x564866efa259 base::debug::CollectStackTrace()
2021-05-13T15:49:54.942759+00:00 app[web.1]: #1 0x564866e669e3 base::debug::StackTrace::StackTrace()
2021-05-13T15:49:54.942759+00:00 app[web.1]: #2 0x564866ef9e00 base::debug::(anonymous namespace)::StackDumpSignalHandler()
2021-05-13T15:49:54.942760+00:00 app[web.1]: #3 0x7fcf7f2d03c0 (/usr/lib/x86_64-linux-gnu/libpthread-2.31.so+0x153bf)
2021-05-13T15:49:54.942760+00:00 app[web.1]: #4 0x7fcf7d96518b gsignal
2021-05-13T15:49:54.942760+00:00 app[web.1]: #5 0x7fcf7d944859 abort
2021-05-13T15:49:54.942760+00:00 app[web.1]: #6 0x564866ef9425 base::debug::BreakDebugger()
2021-05-13T15:49:54.942760+00:00 app[web.1]: #7 0x564866e77a37 logging::LogMessage::~LogMessage()
2021-05-13T15:49:54.942761+00:00 app[web.1]: #8 0x564866e780ce logging::LogMessage::~LogMessage()
2021-05-13T15:49:54.942761+00:00 app[web.1]: #9 0x564866f2dde3 base::trace_event::MemoryDumpManager::GetOrCreateBgTaskRunnerLocked()
2021-05-13T15:49:54.942781+00:00 app[web.1]: #10 0x564866f2dd32 base::trace_event::MemoryDumpManager::GetDumpThreadTaskRunner()
2021-05-13T15:49:54.942782+00:00 app[web.1]: #11 0x5648654cdf31 content::InitializeBrowserMemoryInstrumentationClient()
2021-05-13T15:49:54.942782+00:00 app[web.1]: #12 0x564866e06fce content::ContentMainRunnerImpl::RunBrowser()
2021-05-13T15:49:54.942782+00:00 app[web.1]: #13 0x564866e06c5d content::ContentMainRunnerImpl::Run()
2021-05-13T15:49:54.942782+00:00 app[web.1]: #14 0x564866e0429d content::RunContentProcess()
2021-05-13T15:49:54.942783+00:00 app[web.1]: #15 0x564866e04c3d content::ContentMain()
2021-05-13T15:49:54.942783+00:00 app[web.1]: #16 0x564866e60c29 headless::HeadlessBrowserMain()
2021-05-13T15:49:54.942783+00:00 app[web.1]: #17 0x564866e6093a headless::HeadlessShellMain()
2021-05-13T15:49:54.942783+00:00 app[web.1]: #18 0x564863e913e1 ChromeMain
2021-05-13T15:49:54.942784+00:00 app[web.1]: #19 0x7fcf7d9460b3 __libc_start_main
2021-05-13T15:49:54.942784+00:00 app[web.1]: #20 0x564863e9122a _start
2021-05-13T15:49:54.942784+00:00 app[web.1]: r8: 0000000000000000 r9: 00007ffefdad4510 r10: 0000000000000008 r11: 0000000000000246
2021-05-13T15:49:54.942784+00:00 app[web.1]: r12: 0000025400304000 r13: 00007ffefdad4770 r14: 0000025400304010 r15: aaaaaaaaaaaaaaaa
2021-05-13T15:49:54.942784+00:00 app[web.1]: di: 0000000000000002 si: 00007ffefdad4510 bp: 00007ffefdad4760 bx: 00007fcf7c5a8500
2021-05-13T15:49:54.942784+00:00 app[web.1]: dx: 0000000000000000 ax: 0000000000000000 cx: 00007fcf7d96518b sp: 00007ffefdad4510
2021-05-13T15:49:54.942785+00:00 app[web.1]: ip: 00007fcf7d96518b efl: 0000000000000246 cgf: 630a000000000033 erf: 0000000000000000
2021-05-13T15:49:54.942785+00:00 app[web.1]: trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
2021-05-13T15:49:54.942785+00:00 app[web.1]: [end of stack trace]
2021-05-13T15:49:54.942785+00:00 app[web.1]: Calling _exit(1). Core file will not be generated.
2021-05-13T15:49:54.942785+00:00 app[web.1]:
2021-05-13T15:49:54.942785+00:00 app[web.1]:
2021-05-13T15:49:54.942786+00:00 app[web.1]: TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
2021-05-13T15:49:54.942786+00:00 app[web.1]:
2021-05-13T15:49:54.942786+00:00 app[web.1]: at onClose (/app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:194:20)
2021-05-13T15:49:54.942786+00:00 app[web.1]: at ChildProcess.<anonymous> (/app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:185:79)
2021-05-13T15:49:54.942786+00:00 app[web.1]: at ChildProcess.emit (events.js:327:22)
2021-05-13T15:49:54.942787+00:00 app[web.1]: at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
My question is the following: Is there a way to cancel incoming requests if there is already one being processed? (AKA have the following clicks on the button that send the POST requests NOT register). Alternatively, is there a way to cancel requests that are currently processing?
Finally, is that Puppeteer error thrown because the url that I'm scraping from (Google) is detecting it's a bot opening the browser so it shuts down requests for a limited time? (I think this is what's causing it, but I'm not sure).
I've implemented a pool that releases the client at the end of the function, because I thought that might be causing the memory leak but it appears that's not the problem, so I'm wondering if this could be, thanks!

Node.JS app crash on startup after second deployment on Heroku

I did git push heroku master for the second time.
But I got the error cannot find module ....
For the first time, I succeeded.
How can I fix this? Thanks.
2021-01-03T16:03:35.301824+00:00 app[web.1]: internal/modules/cjs/loader.js:818
2021-01-03T16:03:35.301837+00:00 app[web.1]: throw err;
2021-01-03T16:03:35.301837+00:00 app[web.1]: ^
2021-01-03T16:03:35.301837+00:00 app[web.1]:
2021-01-03T16:03:35.301838+00:00 app[web.1]: Error: Cannot find module './stringToParts'
2021-01-03T16:03:35.301838+00:00 app[web.1]: Require stack:
2021-01-03T16:03:35.301839+00:00 app[web.1]: - /app/node_modules/mpath/lib/index.js
2021-01-03T16:03:35.301839+00:00 app[web.1]: - /app/node_modules/mpath/index.js
2021-01-03T16:03:35.301839+00:00 app[web.1]: - /app/node_modules/mongoose/lib/utils.js
2021-01-03T16:03:35.301840+00:00 app[web.1]: - /app/node_modules/mongoose/lib/statemachine.js
2021-01-03T16:03:35.301841+00:00 app[web.1]: - /app/node_modules/mongoose/lib/internal.js
2021-01-03T16:03:35.301841+00:00 app[web.1]: - /app/node_modules/mongoose/lib/document.js
2021-01-03T16:03:35.301841+00:00 app[web.1]: - /app/node_modules/mongoose/lib/index.js
2021-01-03T16:03:35.301842+00:00 app[web.1]: - /app/node_modules/mongoose/index.js
2021-01-03T16:03:35.301842+00:00 app[web.1]: - /app/models/user.js
2021-01-03T16:03:35.301843+00:00 app[web.1]: - /app/controllers/usersController.js
2021-01-03T16:03:35.301843+00:00 app[web.1]: - /app/routes/userRoutes.js
2021-01-03T16:03:35.301844+00:00 app[web.1]: - /app/routes/index.js
2021-01-03T16:03:35.301845+00:00 app[web.1]: - /app/main.js
2021-01-03T16:03:35.301845+00:00 app[web.1]: at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
2021-01-03T16:03:35.301846+00:00 app[web.1]: at Function.Module._load (internal/modules/cjs/loader.js:667:27)
2021-01-03T16:03:35.301846+00:00 app[web.1]: at Module.require (internal/modules/cjs/loader.js:887:19)
2021-01-03T16:03:35.301847+00:00 app[web.1]: at require (internal/modules/cjs/helpers.js:74:18)
2021-01-03T16:03:35.301847+00:00 app[web.1]: at Object.<anonymous> (/app/node_modules/mpath/lib/index.js:1:21)
2021-01-03T16:03:35.301848+00:00 app[web.1]: at Module._compile (internal/modules/cjs/loader.js:999:30)
2021-01-03T16:03:35.301848+00:00 app[web.1]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
2021-01-03T16:03:35.301849+00:00 app[web.1]: at Module.load (internal/modules/cjs/loader.js:863:32)
2021-01-03T16:03:35.301849+00:00 app[web.1]: at Function.Module._load (internal/modules/cjs/loader.js:708:14)
2021-01-03T16:03:35.301849+00:00 app[web.1]: at Module.require (internal/modules/cjs/loader.js:887:19) {
2021-01-03T16:03:35.301850+00:00 app[web.1]: code: 'MODULE_NOT_FOUND',
2021-01-03T16:03:35.301850+00:00 app[web.1]: requireStack: [
2021-01-03T16:03:35.301851+00:00 app[web.1]: '/app/node_modules/mpath/lib/index.js',
2021-01-03T16:03:35.301851+00:00 app[web.1]: '/app/node_modules/mpath/index.js',
2021-01-03T16:03:35.301851+00:00 app[web.1]: '/app/node_modules/mongoose/lib/utils.js',
2021-01-03T16:03:35.301852+00:00 app[web.1]: '/app/node_modules/mongoose/lib/statemachine.js',
2021-01-03T16:03:35.301852+00:00 app[web.1]: '/app/node_modules/mongoose/lib/internal.js',
2021-01-03T16:03:35.301852+00:00 app[web.1]: '/app/node_modules/mongoose/lib/document.js',
2021-01-03T16:03:35.301853+00:00 app[web.1]: '/app/node_modules/mongoose/lib/index.js',
2021-01-03T16:03:35.301853+00:00 app[web.1]: '/app/node_modules/mongoose/index.js',
2021-01-03T16:03:35.301853+00:00 app[web.1]: '/app/models/user.js',
2021-01-03T16:03:35.301854+00:00 app[web.1]: '/app/controllers/usersController.js',
2021-01-03T16:03:35.301854+00:00 app[web.1]: '/app/routes/userRoutes.js',
2021-01-03T16:03:35.301855+00:00 app[web.1]: '/app/routes/index.js',
2021-01-03T16:03:35.301855+00:00 app[web.1]: '/app/main.js'
2021-01-03T16:03:35.301855+00:00 app[web.1]: ]
2021-01-03T16:03:35.301856+00:00 app[web.1]: }
2021-01-03T16:03:35.394395+00:00 heroku[web.1]: Process exited with status 1
2021-01-03T16:03:35.475189+00:00 heroku[web.1]: State changed from starting to crashed
2021-01-03T16:03:35.479175+00:00 heroku[web.1]: State changed from crashed to starting
2021-01-03T16:03:39.720428+00:00 heroku[web.1]: Starting process with command `node main.js`
Are you exporting the data in './stringToParts' correctly?
When you require a module like './stringToParts', it must be exported.
Check if you have something like this at the end of your './stringToParts' file:
module.exports = function;

Resources