Az.js | A NLP library for Russian language

You can see the error that you are getting if you open your browser's developer tools. I ran your app locally and saw the following error: Uncaught (in promise) Error: [svelte-i18n] Cannot format a message without first setting the initial locale.

The issue is that you are using register to load your dictionaries and trying to retrieve messages before the dictionaries are ready. This method runs asynchronously, so your locales might not be loaded by the time the Svelte template renders. You have two options:

1. Load the dictionaries synchronously using addMessages in your entry point. This way you don't have to wait for the dictionaries to load in order to retrieve messages.

I would recommend using #locale.language to get only the language portion of the context's locale - especially since that is what you need to match for the JS file name.

So, something like this:

Well, your question is an opinion-based one so deciding which approach is better is a bit complicated. But for making a decision you can consider some notes.

• If you are using a lazy load for loading your child components within your parent ones, it is better to import your assets right in the exact component that using those assets. You may ask why? Because Webpack will chunk them into separate bundles, so the assets will only load when the child component gets loaded. So if during code-splitting process user did not reach the specific part of the page where the child component exists, the assets won't load either. It may boost app performance in some cases.
• On the other hand, let's say you do not use lazy loading and don't care about it at all, then it doesn't matter where you importing your assets because whenever the parent component gets loaded the children will load with it in the first place. So it won't make any difference where you import your assets.

We do not need to use Code splitting and lazy loading always in every single application that we working on, it is good but not necessary. So When you are working on a medium to large scale apps you may consider using these methods where they will enhance the app performance.

It is not possible. Based on pm2-logrotate author:

It's not possible apparently since pm2-logrotate is different than pm2, pm2 is not aware beforehand if pm2-lr is already installed or not.

Source: https://github.com/keymetrics/pm2-logrotate/issues/131

Turns out there are two emcc compiler options to disable the asynchronous startup/loading behaviour: -s BINARYEN_ASYNC_COMPILATION=0 and -s SINGLE_FILE=1. This solves the problem for me.

From the related GitHub issue:

In general emscripten tries to do startup asynchronously for wasm, because it's what browsers can best optimize, and worse, Chrome currently has a limitation on the size of synchronous compilations (hopefully will be fixed soon). But you can force sync compilation with -s BINARYEN_ASYNC_COMPILATION=0.

That still leaves fetching the wasm binary file. By default we fetch it asynchronously, but if you have a way to get it yourself before, you can set it on Module['wasmBinary'] and we will just use that synchronously. Alternatively, #5296 will add an option to embed that file, making it available synchronously.

To recap your requirements:

the first reason is pm2 start app.js start the application in background so that is why your container stops as soon as it runs pm2 start.

You need to start an application with pm2_runtime, it starts an application in the foreground. also you do not need concurrently, pm2 process.yml will do this job.

Docker Integration

Using Containers? We got your back. Start today using pm2-runtime, a perfect companion to get the most out of Node.js in production environment.

The goal of pm2-runtime is to wrap your applications into a proper Node.js production environment. It solves major issues when running Node.js applications inside a container like:

Second Process Fallback for High Application Reliability Process Flow Control Automatic Application Monitoring to keep it always sane and high performing Automatic Source Map Discovery and Resolving Support

docker-pm2-nodejs

The second important thing, you should put all your application in pm2 config file, as docker can only run the process from CMD.

Ecosystem File

PM2 empowers your process management workflow. It allows you to fine-tune the behavior, options, environment variables, logs files of each application via a process file. It’s particularly useful for micro-service based applications.

pm2 config application-declaration Create file process.yml

Some thoughts on your approach:

I want to have some important application data (like the route name) in each application manifest and having the host application read them.

Why does a child app have to know about its router configuration in the manifest.json? Your host application is responsible for orchestrating all your children apps. It is the one, which should know the mapping of routes to the specific child apps.

To go a bit more into detail: There is probably a reason, why you have the child apps isolated in the first place - they are self-sufficient and independent from each other and the host. E.g. imagine, you could want to reuse one of the apps and run them as a stand-alone app. That is also the reason, why it is not ideal to go the other way to let the children register them selves in the host. Because this would enforce tighter coupling between the child and host - the child would have to know, that it is used in some bigger application.

Concerning the child app, it can just export some runnable callback, which will be invoked by the host, if the route matches. In your case with React, it could be sufficient to export a ReactElement which will be rendered by the host. This entry point also could have been created in form of a bundle process with Webpack.

Create a file index.js inside foo as follows: