The problem that the absolute path is normal is often invalid when the relative path is used for file loading by require.

The path of the file to be included has already been set to include_path through set_include_path, and then the relative path of the file directly written when the file is loaded using require. Normally, the program can automatically load files in require according to include_path, but now... the path of the file to be included has been set to include_path through set_include_path,

Then use require to load the file, and then directly write the relative path of the file,

Normally, the program can automatically load files in require according to include_path,

But now the problem is that this method is often valid and often fails. That is to say, sometimes loading fails, but refresh and loading is successful.

This problem does not occur if you directly use the absolute path of the file in require.

Reply content:

The path of the file to be included has been set to include_path through set_include_path,

Then use require to load the file, and then directly write the relative path of the file,

Normally, the program can automatically load files in require according to include_path,

But now the problem is that this method is often valid and often fails. That is to say, sometimes loading fails, but refresh and loading is successful.

This problem does not occur if you directly use the absolute path of the file in require.

Is it valid for a while loading files on the same page?