js-to-c | A compiled implementation of Javascript , targetting C | Runtime Evironment library

The script tag is in html it will not run in php block so you have to close your php block before script tag and open php block after script tag

The reason for the message npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained is because parcel-bundler has a transitive dependency on core-js@2.6.11, which is no longer supported.

It appears that parcel was installed correctly, so you should be able to run it. On Linux systems, it would have created a symlink under /usr/local/bin/parcel. Make sure that "/usr/local/bin" is in your PATH.

You can also run it as follows:

1. There are two onMessage listeners in the background script, so you need to combine them into one, otherwise only the first one will be able to send a response
2. The extension API is asynchronous so the callback runs after the surrounding code has already finished, meaning sendResponse(hashtagInput) won't do anything. You should replace the subsequent sendResponse(userHash) with return true so onMessage will keep the channel open and replace sendResponse(hashtagInput) with something that sends both variables in one object e.g. sendResponse({userHash, hashtagInput}) and of course the messaging caller should be changed to reflect that as well
3. Currently all sendResponse are sending data into nothing because there's no callback parameter in sendMessage, see the messaging documentation for examples.
4. The background script runs in a hidden separate background page, which is empty and not related to the browser action popup, so there'll be no DOM elements like #hashtagInput and updateCount will be null.
5. The only thing you need in the background script is chrome.tabs.onUpdated listener so remove everything else.
6. Write to the storage in the popup script

7. Send a message to the tab in the popup script, for example:

When you have connection reset it means usually that nobody is listen on the port .

It seems you are listening on localhost , you must listening on 0.0.0.0 when you are in the docker .

in your file config/index.js , host is localhost , you must remove the host directive

If you listening on 127.0.0.1or localhost , you are listening on local network , so inside the container , the web server can be accessed only by local process .

Another source of problems you can have , you are connecting to the wrong port .

if you run with docker run -it -p 8081:8080 you must acces to http://localhost:8081/

see

Publish or expose port (-p, --expose) from https://docs.docker.com/engine/reference/commandline/run/

Have you tried with a simple if condition?

I have no idea what your architecture looks like, but here is a potential solution that will work to solve your problem.

The solution uses the Web Worker API to off load the file uploading to a sub-process. This is done with the Worker Interface of that API. This approach will work because there is no contention of the single thread of the main process - web workers work in their own processes.

Using this approach, we do three basic things:

1. create a new worker passing a script to execute
2. pass messages to the worker for the worker to deal with
3. pass messages back to the main process for status updates/replies/resolved data transformation/etc.

The code is heavily commented below to help you understand what is happening and where.

This is the main JavaScript file (script.js)

The requirement property gets set to true or false immediately on the object's declaration - after it's been evaluated the first time, it doesn't change itself spontaneously. You want a function that you can call that returns a boolean, instead of a static boolean value: