The way to get this to work depends on your package manager: However, people sometimes get into this situation by installing esbuild on Windows or macOS and copying their node_modules directory into a Docker image that runs Linux, or by copying their node_modules directory between Windows and WSL environments.
#Runjs vs npm install#
Normally this isn't an issue because you typically check your package.json file into version control, not your node_modules directory, and then everyone runs npm install on their local machine after cloning the repository. This won't work because esbuild is written with native code and needs to install a platform-specific binary executable.
You cannot install esbuild on one OS, copy the node_modules directory to another OS without reinstalling, and then run esbuild on that other OS. If you do this, your dependencies must still be present on the file system at run-time since they are no longer included in the bundle. A natural way of doing this is to add a build script to your package.json file like this: , Your build command is something you will be running repeatedly, so you will want to automate it. You can read more about the available configuration options in the API documentation. js files instead, you can tell esbuild to allow this using the -loader.js=jsx flag. While esbuild can be configured, it attempts to have reasonable defaults so that many common situations work automatically. Notice that esbuild also converted JSX syntax to JavaScript without any configuration other than the.
If you run the code using node out.js, you should see something like this: Hello, world! The code is completely self-contained and no longer depends on your node_modules directory. This should have created a file called out.js containing your code and the React library bundled together. \node_modules\.bin\esbuild app.jsx -bundle -outfile=out.js node_modules/.bin/esbuild app.jsx -bundle -outfile=out.js.
0 kommentar(er)
