如何从服务器下载 js 文件并运行它？

Question

Is it possible to run a js file locally that downloads a secondary file and then run the latter?

I know the best thing would be to download the file from the server and save it locally, I would just like to understand if there is still the possibility to do the above.

Example:

Open terminal

1- node index js

2 - download scripts js in the same directory as index.js

3 - download is complete, start script js automatically.

Answer 1

Even if it is possible to solve it with Node.js workarounds (like requireing your puppeteer script from an url etc.) I strongly suggest to use Git with your team to share the latest version of your script. Version control is a must in modern software development, especially if you are working in a team. By learning the 6-7 most basic git commands you can solve almost everything you need for the current use case.

There are many good tutorials how to get started with git, I recommend GitHub's https://try.github.io .

Of course: you need to convince your team to embrace the change, or in better case they are already using it for version control, so it will be familiar to them.

You will need to:

1. Install Git locally;
2. Create a new repository on a server where you can store the latest stable versions of all your scripts (if it is not an open source project make sure it is private, GitLab; GitHub and Bitbucket provides/hosts free private repositories that will suit your needs);
3. Share the HTTPS (or SSH) URL of the repository with your team (eg: https://github.com/.../puppeteer-scripts.git ) which they can clone;
4. Make sure your changes are pushed to the remote git repository;
5. Your team can pull the latest changes to their local computer (it will be their responsiblity to check if there were changes in the scripts, but you can notify them as well - there are automatic notifications if one starts to "watch" a git repository);

---

Lastly

Git can be frightening at first sight, but it can be learned in a few days and it makes code sharing smooth within your team.

One of Git's tagline describes very well why it will solve your problem:

--everything-is-local