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

After the project is packaged and deployed to the production environment, the physical path can be viewed in the browser, source code/source section. How to avoid the physical path in the JS file??? #11180

Closed
lander123 opened this issue Jun 5, 2024 · 2 comments
Labels
kind/question QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this

Comments

@lander123
Copy link

After the project is packaged and deployed to the production environment, the physical path can be viewed in the browser, source code/source section. How to avoid the physical path in the JS file???
image

@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jun 5, 2024
@richard-cox
Copy link
Member

What branch are you building from, and how are you building the UI?

Would you be able to expand on why you need to build it locally?

@richard-cox
Copy link
Member

No additional information, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

2 participants