About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
missing_linux_example
⚠️
windows_tools
Summary:
The documentation demonstrates a Windows bias by providing setup instructions and examples primarily for Windows users. It references Windows-specific tools and paths (e.g., PowerShell commands, C:\ paths), and links to Windows-focused setup guides. There are no equivalent instructions or examples for Linux or macOS users, and the workflow assumes familiarity with Windows conventions.
Recommendations:
- Provide parallel setup instructions for Linux and macOS, including terminal commands for nvm and Node.js installation on those platforms.
- Include example shell commands (bash/zsh) alongside PowerShell commands, and clarify which commands are cross-platform.
- Use platform-agnostic file paths in examples, or provide both Windows (C:\Users\...) and Unix-style (~/ or /home/user/...) paths.
- Link to official nvm and Node.js installation guides for Linux and macOS, not just Windows.
- Mention that Visual Studio Code and the Azure extensions are available on all major platforms, and provide any platform-specific installation tips.
- Ensure screenshots and instructions for deploying or running commands in the terminal are not exclusively Windows-focused.
Create pull request
Flagged Code Snippets
This action adds the Azure Communication Services common and calling packages as dependencies of your package. You'll see two new packages added to the `package.json` file. You can find more information about `npm install` on the [npm Docs page for that command](https://docs.npmjs.com/cli/v6/commands/npm-install).
:::image type="content" source="./media/step-one-pic-nine.png" alt-text="Screenshot that shows code for installing Azure Communication Services packages.":::
These packages are provided by the Azure Communication Services team and include the authentication and calling libraries. The `--save` command signals that the application depends on these packages for production use and will be included in `devDependencies` within the `package.json` file. When you build the application for production, the packages will be included in your production code.
## Publish your website to Azure static websites
### Create a configuration for production deployment
Add the following code to `webpack.prod.js`:
The console shows you where the server is running. By default, it's `http://localhost:8080`. The `build:dev` command is the command that you added to `package.json` earlier.
:::image type="content" source="./media/step-one-pic-16.png" alt-text="Screenshot that shows starting a development server.":::
Go to the address in your browser, and you should see the page and alert configured in previous steps.
:::image type="content" source="./media/step-one-pic-17.png" alt-text="Screenshot of the H T M L page.":::
While the server is running, you can change the code and the server. The HTML page will automatically reload.
Next, go to the `app.js` file in Visual Studio Code and delete `alert('Hello world alert!');`. Save your file and verify that the alert disappears from your browser.
To stop your server, you can run `Ctrl+C` in your terminal. To start your server, enter `npm run build:dev` at any time.
## Add the Azure Communication Services packages
Use the `npm install` command to install the Azure Communication Services Calling SDK for JavaScript.
The command creates a `dist` folder and a production-ready `app.js` static file in it.
:::image type="content" source="./media/step-one-pic-21.png" alt-text="Screenshot that shows the production build.":::
### Deploy your app to Azure Storage
Copy `index.html` and `app.css` to the `dist` folder.
In the `dist` folder, create a file and name it `404.html`. Copy the following markup into that file: