feat: Custom dev ui port(load env from .env)

[FrankFang]

OS: Windows 10
When I run yarn start, I get Something is already running on port 3000..
It's good if I can customize the dev port.

P.S. I am sure there is no server running on port 3000 because I just restarted my computer. Maybe something is broken but I no time to figure it out, so custimzation of port is needed for me.

[FrankFang]

I update a lot of code:

1. Create neuron-shared as a shared package
2. Add load-env.ts into neuron-shared and test it
3. Upgrade dotenv from 8 to 16.1.4
4. Use loadEnv to get env vars anywhere

[FrankFang]

It's late now, I'm going to sleep. I'll fix these later.

[FrankFang]

Most are fixed but not 'node:fs’

[FrankFang]

dotenvExpand makes ENV_2=${ENV_1} possible.

[yanguoyu]

With the PR, we can not auto-start ui with another port when run the command yarn start:ui if the default port has been used. And if the 3000 port has been used, we cannot get any help from the output. The neuron-wallet only waits for http://127.0.0.1:3000 because the neuron-ui does not throw any exceptions with the used port.

[FrankFang]

The neuron-wallet only waits for http://127.0.0.1:3000

I've change the start task for neuron-wallet

"start": "node scripts/wait-ui.mjs && yarn run start:debug

So neuron-wallet could wait for http://127.0.0.1:${PORT} now.

[WhiteMinds]

My main concern currently is to avoid introducing the complexity of neuron-shared too early. At the moment, it only provides a unified rule for loading envFiles.
Which we can achieve using libraries like @next/env. This way, we can directly implement the same logic in both packages through simple code duplication, without the need for a new package implementation.

@Keith-CY @yanguoyu @devchenyan @JeffreyMa597 @homura , what do you think?

If we all agree to introduce neuron-shared, there are a few tasks that need to be done:

1. Automatically compile on the first yarn, similar to this: https://github.com/nervosnetwork/neuron/blob/e7adec4b89ce9976ba9d598960a50f7dce176cff/package.json#LL38C38-L38C87
2. Like neuron-wallet and neuron-ui, include Prettier and ESLint.
3. Optionally, rename main.ts to a more conventional index.ts

[Keith-CY]

My main concern currently is to avoid introducing the complexity of neuron-shared too early. At the moment, it only provides a unified rule for loading envFiles. Which we can achieve using libraries like @next/env. This way, we can directly implement the same logic in both packages through simple code duplication, without the need for a new package implementation.

@Keith-CY @yanguoyu @devchenyan @JeffreyMa597 @homura , what do you think?

If we all agree to introduce neuron-shared, there are a few tasks that need to be done:

1. Automatically compile on the first yarn, similar to this: e7adec4/package.json#LL38C38-L38C87
2. Like neuron-wallet and neuron-ui, include Prettier and ESLint.
3. Optionally, rename main.ts to a more conventional index.ts

It may be cumbersome to share an env through a package, it can be done simply by extending envs from the project root.

[WhiteMinds]

It may be cumbersome to share an env through a package, it can be done simply by extending envs from the project root.

Currently, we are not sharing the environment variables themselves, but rather the loadEnv function. In reality, the environment configuration for each project is still independent. Therefore, I believe introducing this complexity (neuron-shared) is unnecessary.

[yanguoyu]

It may be cumbersome to share an env through a package, it can be done simply by extending envs from the project root.

Currently, we are not sharing the environment variables themselves, but rather the loadEnv function. In reality, the environment configuration for each project is still independent. Therefore, I believe introducing this complexity (neuron-shared) is unnecessary.

I strongly agree, and lerna can auto-load environment files when running tasks with lerna. https://lerna.js.org/docs/features/run-tasks#automatic-loading-of-env-files

[github-actions]

Packaging for test is done in 5320392944 for commit 36c1621 .

[Keith-CY]

Will this PR be updated according to the comments above?