Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

easm failed to generate apiView #2404

Closed
MaryGao opened this issue Apr 3, 2024 · 6 comments · Fixed by Azure/azure-sdk-tools#8031 or #2426
Closed

easm failed to generate apiView #2404

MaryGao opened this issue Apr 3, 2024 · 6 comments · Fixed by Azure/azure-sdk-tools#8031 or #2426
Assignees
Labels

Comments

@kazrael2119
Copy link
Contributor

@MaryGao
Copy link
Member Author

MaryGao commented Apr 8, 2024

@kazrael2119
Copy link
Contributor

kazrael2119 commented Apr 9, 2024

Compared with the easm script and other rlc scripts(@azure-rest/arm-appservice), it was found that the following scripts are missing from the easm script:

    "build:browser": "tsc -p . && dev-tool run bundle",
    "build:node": "tsc -p . && dev-tool run bundle --browser-test false",
    "build:test": "tsc -p . && dev-tool run bundle",
    "build:debug": "tsc -p . && dev-tool run bundle && api-extractor run --local",
    "extract-api": "rimraf review && mkdirp ./review && api-extractor run --local",
    "integration-test": "npm run integration-test:node && npm run integration-test:browser",
    "pack": "npm pack 2>&1",
    "unit-test": "npm run unit-test:node && npm run unit-test:browser",

@kazrael2119
Copy link
Contributor

Compared with the easm script and other mgmt package(@azure/arm-frontdoor), it was found that the following scripts are missing from the easm script:

"prepack": "npm run build",
"pack": "npm pack 2>&1",
"extract-api": "api-extractor run --local",
"integration-test": "npm run integration-test:node && npm run integration-test:browser",
"unit-test": "npm run unit-test:node && npm run unit-test:browser",

@MaryGao
Copy link
Member Author

MaryGao commented Apr 9, 2024

@kazrael2119 Could you help add following 4 entries in scripts? @joheredi Not sure any reason we missed them but if failed ci .

    "extract-api": "rimraf review && mkdirp ./review && api-extractor run --local",
    "integration-test": "npm run integration-test:node && npm run integration-test:browser",
    "pack": "npm pack 2>&1",
    "unit-test": "npm run unit-test:node && npm run unit-test:browser",

@kazrael2119
Copy link
Contributor

kazrael2119 commented Apr 9, 2024

browser test failed with following message:

$ rushx unit-test:browser
Found configuration in D:\test\azure-sdk-for-js\rush.json

Rush Multi-Project Build Tool 5.112.1 - Node.js 18.19.0 (LTS)
> "npm run build:test && dev-tool run test:vitest --no-test-proxy --browser"


> @azure-rest/[email protected] build:test
> npm run clean && tshy && dev-tool run build-test


> @azure-rest/[email protected] clean
> rimraf --glob dist dist-browser dist-esm test-dist temp types *.tgz *.log

[build-test] The file tsconfig.browser.config.json does not exist.
[dev-tool] Errors occured. See the output above.
Error: Failed calling npm run build:test && dev-tool run test:vitest --no-test-proxy --browser.  Exit code: 1

@qiaozha qiaozha added HRLC p0 priority 0 labels Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants