Azure / Azure/api-management-developer-portal

Source maps still visible on publish

Open
#2,278 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
545
Forks
360
PR merge metrics
No merged PRs in 30d

Description

## Bug description

I'm trying to disable source maps on production. Whats the best way to do this? I already tried this in `webpack.publisher.js` (which im using) by adding this line to the `publisherConfig`: `devtool: "hidden-nosources-source-map"` but no luck.

In my package.json im calling a script with the following value : `webpack --config webpack.publisher.js && node dist/publisher/index.js` to create the html pages.

## Expected behavior

No source maps on our environment

## Is your portal managed or self-hosted?

Self-hosted

## Release tag or commit SHA (if using self-hosted version)

2.24.0

## API Management service name

no

## Environment

- Operating system: Windows
- Browser: Chrome / Edge
- Version: latest

## Additional context
sources are avaiable through the browser devtools:

image

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the publish command from package.json: webpack --config webpack.publisher.js && node dist/publisher/index.js. Read webpack.publisher.js and the publisherConfig, then inspect the generated dist/publisher output in browser devtools. Done means the self-hosted production pages no longer expose source maps.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, webpack
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.