microsoft / microsoft/Dynamics365Commerce.Solutions
CSU/CPOS: Broken source maps
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 80
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
Debugging Issue
Summary
After deploying a CSU and CPOS for development on a devbox the CPOS fails to load the sourcemaps for typescript written in the extension project.
Commerce SDK Version: 9.50.24191.3
Visual Studio/Visual Studio Code:
Visual Studio 2022 toolchain
I do not use Visual studio code as it is unable to consistently build the project
Reproducing the Issue
- Install the sample CSU at https://github.com/microsoft/Dynamics365Commerce.ScaleUnit/tree/release/9.50 to a location on the K drive.
- Log into the Cloud POS associated with that CSU
- Open the developer console
- Open the sources tab
- Open the NavigateToExampleViewCommand.js file
- At the bottom of the file it will state that it could not find the source mapping and the source mapping URL will be a path to the .js.map file on the K drive
Screenshots
The extension is installed via the install script provided in the sample project and either done via a simple script or invoked from vscode.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by installing the sample CSU from the release/9.50 project, opening Cloud POS developer tools, and inspecting NavigateToExampleViewCommand.js in Sources. Check how the install script exposes the generated .js.map path on the K drive. Done means the CPOS source map loads the TypeScript source without the mapping failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100