azure-sdk-for-js/.gitignore

198 строки
2.5 KiB
Plaintext
Исходник Обычный вид История

2019-05-06 21:14:43 +03:00
## BEGIN Rush .gitignore
# Logs
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
# Runtime data
*.pid
*.seed
*.pid.lock
# Default Assets restore directory
.assets
2019-05-06 21:14:43 +03:00
# Directory for instrumented libs generated by jscoverage/JSCover
lib-cov
# Coverage directory used by tools like istanbul
coverage
coverage-browser
# nyc test coverage
.nyc_output
# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
.grunt
# Bower dependency directory (https://bower.io/)
bower_components
# node-waf configuration
.lock-wscript
# Compiled binary addons (https://nodejs.org/api/addons.html)
build/Release
# Dependency directories
node_modules/
jspm_packages/
# Optional npm cache directory
.npm
# Optional eslint cache
.eslintcache
# Optional REPL history
.node_repl_history
# Output of 'npm pack'
*.tgz
# Yarn Integrity file
.yarn-integrity
# dotenv environment variables file
*.env
!sample.env
!test.env
2019-05-06 21:14:43 +03:00
# next.js build output
.next
# Common toolchain intermediate files
temp
# Rush files
common/temp/**
package-deps.json
common/autoinstallers/*/.npmrc
2019-05-06 21:14:43 +03:00
## END Rush .gitignore
projects/*
targets/*
test/data/test_package.zip
# Nuget packages and corresponding codegen sources
.nuget
packages
# Visual Studio #
*.suo
*.user
.ntvs_analysis.dat
obj/*
examples/obj
examples/.ntvs_analysis.dat
examples/.vs
examples/bin
.vs
TestResults/*
.vscode/*
./**/.vscode/*
# Node #
**/node_modules/
**/cjs/
**/esm/
**/lib/**/*.js
**/lib/**/*.js.map
**/*Bundle.js
**/*Bundle.js.map
**/package-lock.json
**/yarn.lock
2019-05-06 21:14:43 +03:00
npm-debug.log.*
azure_error
checkstyle-result.xml
test-result.xml
test-results.*xml
**/cjs/
**/esm/
# Mac OS #
.DS_Store
.DS_Store?
# Windows #
Thumbs.db
# Credentials #
*.cer
*.pfx
*.pem
*.key
*.srl
2019-05-06 21:14:43 +03:00
# WebStorm #
.idea/
# docs #
docs/
!eng/scripts/docs
2019-05-06 21:14:43 +03:00
main.conf.json
child.conf.json
docGen/
2019-05-06 21:14:43 +03:00
# temporary test artifacts
test/tmp/*
common/smoke-test/run-manifest.json
2019-05-06 21:14:43 +03:00
# build artifacts
dist
dist-*
test-dist
test-dist*
test-browser
typings
typedoc
types
es
sdk/cosmosdb/cosmos/lib
*.test.js
*.test.js.map
*lintReport.html
tsdoc-metadata.json
2019-05-06 21:14:43 +03:00
Integrate Asset-Sync Features (#23405) * updating create recording request * first draft. need to integrate node tests and then reach out to harsha * commiting prettier update * repair ascension algo * add initial assets.json. update gitignore. * move textanalytics recordings. time to try the node tests! * remaining recorder updates. properly setting the assets.json path now * using a different version of the proxy to ensure that we include all the bugfixes from recently * bunch of changes for RECORDING_ASSETS_PATH * lint applied * Update sdk/test-utils/recorder/src/utils/utils.ts Co-authored-by: Timo van Veenendaal <timov@microsoft.com> * Update sdk/test-utils/recorder/src/utils/createRecordingRequest.ts Co-authored-by: Timo van Veenendaal <timov@microsoft.com> * Update sdk/test-utils/recorder/src/utils/relativePathCalculator.browser.ts Co-authored-by: Timo van Veenendaal <timov@microsoft.com> * Update sdk/test-utils/recorder/src/utils/utils.ts Co-authored-by: Timo van Veenendaal <timov@microsoft.com> * Update sdk/test-utils/recorder/src/utils/utils.ts * Update sdk/test-utils/recorder/src/utils/createRecordingRequest.ts Co-authored-by: Timo van Veenendaal <timov@microsoft.com> * repair imports * linting commit * resolve failing node tests * handle undefined set in environment variable * commit recordings update now that the source has been updated * fix pipeline * if (!fs.existsSync(assetsPath)) return undefined; * format * fix lint * Some refactors; calculate assets path in browser using existing environment variable * Re-add second environment variable * undo assets changes Co-authored-by: Timo van Veenendaal <timov@microsoft.com> Co-authored-by: Harsha Nalluru <sanallur@microsoft.com>
2022-11-16 02:30:24 +03:00
# locally cloned assets
.assets
2019-05-06 21:14:43 +03:00
# autorest generated files
swagger/*.json
#autorest artifacts
code-model-*
# code workspaces
*.code-workspace
!/dataplane.code-workspace
# CPU profiles
*.cpuprofile
# Temp typespec files
TempTypeSpecFiles/
# Symbolic link from project directory to recordings
_recordings
# CI generated artifacts
/artifacts
sdk/template/template-dpg/src/src
[core] Upgrade to ES-Modules for core (#26238) ### Packages impacted by this PR - @azure/abort-controller - @azure/core-auth - @azure/core-client - @azure-rest/core-client - @azure/core-http-compat - @azure/core-lro - @azure/core-paging - @azure/core-rest-pipeline - @azure/core-sse - @azure/core-tracing - @azure/core-util - @azure/core-xml - @azure/logger - @typespec/ts-http-runtime ### Issues associated with this PR ### Describe the problem that is addressed by this PR This migrates the core packages from a hybrid of CJS and ESM to an ESM solution using [`tshy`](https://github.com/isaacs/tshy). The core is now ESM, implemented as a module, and projects using `tshy` to CommonJS and ESM. The ESM build targets we will target include: - ESM (Node) - Browser - React-Native - Bun - Deno This will allow each system to pick up the correct output instead of picking the browser bundle which has happened in the past. Currently, our bun and deno support is strictly through npm compatibility and we are not forking logic at this point for those runtimes. In order to support ESM, `sinon` does not allow for ESM module mocking, so we looked for an alterative in `vitest`. This PR also migrates all core packages stated above from Mocha/Chai for Node and Mocha/Chai/Karma for the browser to using `vitest` for all tests. Currently, the system builds a test bundle which targets the correct files such as those targeted for the browser, eg `log-browser.mts` becomes `log.js` in the compiled output. ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? ### Are there test cases added in this PR? _(If not, why?)_ ### Provide a list of related PRs _(if any)_ ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ### Checklists - [ ] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [ ] Added a changelog (if necessary) --------- Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com> Co-authored-by: Maor Leger <maorleger@users.noreply.github.com> Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com>
2024-02-20 20:42:23 +03:00
# tshy
.tshy
[core] Upgrade to ES-Modules for core (#26238) ### Packages impacted by this PR - @azure/abort-controller - @azure/core-auth - @azure/core-client - @azure-rest/core-client - @azure/core-http-compat - @azure/core-lro - @azure/core-paging - @azure/core-rest-pipeline - @azure/core-sse - @azure/core-tracing - @azure/core-util - @azure/core-xml - @azure/logger - @typespec/ts-http-runtime ### Issues associated with this PR ### Describe the problem that is addressed by this PR This migrates the core packages from a hybrid of CJS and ESM to an ESM solution using [`tshy`](https://github.com/isaacs/tshy). The core is now ESM, implemented as a module, and projects using `tshy` to CommonJS and ESM. The ESM build targets we will target include: - ESM (Node) - Browser - React-Native - Bun - Deno This will allow each system to pick up the correct output instead of picking the browser bundle which has happened in the past. Currently, our bun and deno support is strictly through npm compatibility and we are not forking logic at this point for those runtimes. In order to support ESM, `sinon` does not allow for ESM module mocking, so we looked for an alterative in `vitest`. This PR also migrates all core packages stated above from Mocha/Chai for Node and Mocha/Chai/Karma for the browser to using `vitest` for all tests. Currently, the system builds a test bundle which targets the correct files such as those targeted for the browser, eg `log-browser.mts` becomes `log.js` in the compiled output. ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? ### Are there test cases added in this PR? _(If not, why?)_ ### Provide a list of related PRs _(if any)_ ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ### Checklists - [ ] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [ ] Added a changelog (if necessary) --------- Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com> Co-authored-by: Maor Leger <maorleger@users.noreply.github.com> Co-authored-by: Jeremy Meng <jeremy.ymeng@gmail.com>
2024-02-20 20:42:23 +03:00
.tshy-build-tmp
.tshy-build
# sshkey
sdk/**/sshKey
sdk/**/sshKey.pub
# vitest results
.vite/vitest/results.json