Azure Static Web Apps extension for VS Code
Перейти к файлу
Alex Weininger ae27ad2942
Bump version, update changelog, and update notice (#820)
* Bump version to 0.12.0

* Update changelog

* Update NOTICE

* Fix links
2023-04-03 16:44:52 -04:00
.azure-pipelines Add build def to name (#817) 2023-03-31 16:50:03 -04:00
.github Rename info-needed-closer (#731) 2022-07-25 13:41:20 -04:00
.husky Add sort pre-commit hook (#533) 2021-10-01 13:35:35 -07:00
.vscode Migration work for vscode.dev (#801) 2023-03-29 11:58:18 -07:00
resources Rename image (#698) 2022-05-23 13:06:20 -07:00
src Activate RemoteRepo if local git is disabled. Also always use RemoteRepos for web (#818) 2023-04-03 16:57:41 +00:00
test Add tests for task provider (#809) 2023-03-29 16:27:06 -04:00
.eslintignore Framework detection (#514) 2021-09-16 14:50:28 -07:00
.eslintrc.js Switch to shared ESLint config (#471) 2021-08-12 10:18:45 -07:00
.gitattributes Create .gitattributes (#576) 2021-11-10 17:39:51 -05:00
.gitignore Init 2020-02-05 13:38:34 -08:00
.nvmrc Add .nvmrc file (#774) 2022-12-07 13:38:39 -08:00
.vscodeignore Prep for release - 0.9.0 (#577) 2021-11-12 12:09:42 -05:00
CHANGELOG.md Bump version, update changelog, and update notice (#820) 2023-04-03 16:44:52 -04:00
CODE_OF_CONDUCT.md Add Code of Conduct and Security docs from template (#353) 2021-04-14 10:57:16 -07:00
LICENSE.md Init 2020-02-05 13:38:34 -08:00
NOTICE.html Bump version, update changelog, and update notice (#820) 2023-04-03 16:44:52 -04:00
README.md Fix readme badges (#751) 2022-10-18 14:16:06 -04:00
SECURITY.md Add Code of Conduct and Security docs from template (#353) 2021-04-14 10:57:16 -07:00
SUPPORT.md Add support.md file (#468) 2021-08-09 09:51:01 -07:00
extension.bundle.ts Add tests for task provider (#809) 2023-03-29 16:27:06 -04:00
gulpfile.ts Migrate to @vscode/test-electron package (#779) 2023-01-17 10:26:24 -08:00
main.js Migration work for vscode.dev (#801) 2023-03-29 11:58:18 -07:00
package-lock.json Bump version, update changelog, and update notice (#820) 2023-04-03 16:44:52 -04:00
package.json Bump version, update changelog, and update notice (#820) 2023-04-03 16:44:52 -04:00
package.nls.json Merge unified into main (#692) 2022-05-13 13:03:30 -07:00
tsconfig.json Turn on "strict" tsconfig rule (#584) 2021-11-15 16:04:34 -05:00
webpack.config.js Migration work for vscode.dev (#801) 2023-03-29 11:58:18 -07:00

README.md

Azure Static Web Apps for Visual Studio Code

Version Installs Build Status

Use this extension to quickly create and manage Azure Static Web Apps directly from VS Code.

Visit the wiki for additional information about the extension.

Sign up today for your free Azure account and receive 12 months of free popular services, $200 free credit and 25+ always free services 👉 Start Free.

Run and debug your static web app

Debug static web app with a dynamic configuration

Check out Guide: Debugging a Static Web App with VS Code for instructions and more information about debugging a static web app.

Create your first static web app

  1. Click the '+' button in the explorer to setup a new static web app

    Create Static Web App

  2. Select "Create Static Web App..."

    Create Static Web App

  3. Authorize access to your GitHub account so the extension can find your repositories

    Authorize Access to through GitHub

    Authorize Access to through GitHub

  4. Select a repository and branch that will be deployed to the static web app

    If your local project has a remote configured, the extension will default to that repository

  5. Provide the app folder name

    Location of your application code. For example, '/' represents the root of your app, while '/app' represents a directory called 'app'.

  6. Provide the api folder name (optional)

    Location of your Azure Functions code. For example, '/api' represents a folder called 'api'. If you don't have an Azure Functions project yet, don't worry! This is optional so just leave this blank.

  7. Provide the build artifact folder name

    The path of your build output relative to your apps location. For example, setting a value of 'build' when your app location is set to '/app' will cause the content at '/app/build' to be served.

See recommended settings for popular frameworks and libraries

Updating your static web app

Commit and push your changes to the GitHub repository that your static web app is configured to. It will then use GitHub Actions to update your app.

If you create a pull request through GitHub, GitHub Actions will create a staging environment with your new changes live. Your Production environment and staging environments are all listed within your Static Web App as well as application settings.

IMPORTANT: The application settings only apply to the backend API of an Azure Static Web App.

Static Web App Environments

Create a HTTP Function for your static web app

You can add a serverless API to your static web app by creating a HTTP Functions project.

  1. Open your static web app project in your Visual Studio Code workspace

  2. Select the button to create a new HTTP Function

    Create HTTP Function

  3. Provide a HTTP Function name that is unique to your API

  4. If this is your first HTTP Function, select a language for your API

Select Language

Contributing

There are a couple of ways you can contribute to this repo:

  • Ideas, feature requests and bugs: We are open to all ideas and we want to get rid of bugs! Use the Issues section to either report a new issue, provide your ideas or contribute to existing threads.
  • Documentation: Found a typo or strangely worded sentences? Submit a PR!
  • Code: Contribute bug fixes, features or design changes:
    • Clone the repository locally and open in VS Code.
    • Run "Extensions: Show Recommended Extensions" from the command palette and install all extensions listed under "Workspace Recommendations"
    • Open the terminal (press Ctrl + `) and run npm install.
    • To build, press F1 and type in Tasks: Run Build Task.
    • Debug: press F5 to start debugging the extension.

Before we can accept your pull request you will need to sign a Contribution License Agreement. All you need to do is to submit a pull request, then the PR will get appropriately labelled (e.g. cla-required, cla-norequired, cla-signed, cla-already-signed). If you already signed the agreement we will continue with reviewing the PR, otherwise system will tell you how you can sign the CLA. Once you sign the CLA all future PR's will be labeled as cla-signed.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Telemetry

VS Code collects usage data and sends it to Microsoft to help improve our products and services. Read our privacy statement to learn more. If you dont wish to send usage data to Microsoft, you can set the telemetry.enableTelemetry setting to false. Learn more in our FAQ.

License

MIT