4feb9b1c72
This makes it easier to experiment with VSCode's [remote development using docker containers][1] feature. In the future, we may check in the necessary files for users to use this feature, but for now ignoring the directory makes it easier play around and evaluate the feature. [1]: https://code.visualstudio.com/docs/remote/containers PR Close #30417
38 lines
525 B
Plaintext
38 lines
525 B
Plaintext
.DS_STORE
|
|
|
|
/dist/
|
|
/bazel-out
|
|
/integration/bazel/bazel-*
|
|
e2e_test.*
|
|
node_modules
|
|
tools/gulp-tasks/cldr/cldr-data/
|
|
|
|
# Include when developing application packages.
|
|
pubspec.lock
|
|
.c9
|
|
.idea/
|
|
.devcontainer
|
|
.settings/
|
|
.vscode/launch.json
|
|
.vscode/settings.json
|
|
*.swo
|
|
modules/.settings
|
|
modules/.vscode
|
|
|
|
# Don't check in secret files
|
|
*secret.js
|
|
|
|
# Ignore npm/yarn debug log
|
|
npm-debug.log
|
|
yarn-error.log
|
|
|
|
# build-analytics
|
|
.build-analytics
|
|
|
|
# rollup-test output
|
|
/modules/rollup-test/dist/
|
|
|
|
# User specific bazel settings
|
|
.bazelrc.user
|
|
|