Comments (3)
Yeah, at the moment the basename is just used. This is to prevent information exposure with the filename path if you were to use the sourcemap in the browser. Do other source maps just include the full local path? If this is the case then it's probably not that big of a deal.
from babel.
Shouldn't that be something that the developer using the API should have control over? It would be easy for the developer to prevent exposure themselves with path.basename
. Another scenario I see is one would want to construct their own path/directory structure instead. (ex: http://example.com/www/js/one.js
) I understand if you want to keep it as is, but either way there should be something documented on that. (whether tips to prevent full directory exposure or a notice that the path gets stripped away in source maps)
from babel.
from babel.
Related Issues (20)
- [Bug]: `@babel/core` peer dependency of `@babel/[email protected]` produces warnings after install HOT 1
- [Bug]: Instance brand checks defined in static class elements do not work when the class is decorated HOT 1
- [Bug]: class decorator context.kind is 'field', should 'class' HOT 2
- [Bug]: Fails to parse Flow conditional type. HOT 3
- [Bug]: decorators 2023-05: `addInitializer` runs initializer at the wrong time HOT 2
- [Bug]: `path.remove`: crash when there is no `parentPath` HOT 1
- [Bug]: hasOwn is not handled properly HOT 3
- [Bug]: Transpilation Bug with Decorators - Incorrectly Passing 'type: parameter' Instead of 'type: class' HOT 3
- [Bug]: decorators are broken and when applied, they override the preceding value. HOT 2
- Improve parse error location? HOT 4
- [Bug]: createRequire is not a function HOT 4
- [Bug]: toPrimitive() does not use the typeof() function HOT 11
- @babel/eslint-plugin: Support ESLint 9 HOT 1
- Types for @babel/eslint-parser and @babel/eslint-plugin HOT 1
- [Slack]: Link broken again HOT 8
- [Bug]: Process correct ts file throw error: expected node to be of a type ["FlowType"] but instead got "TSTypeReference" HOT 5
- [Bug]: rest spread data is lost when @babel/plugin-transform-computed-properties is used alone HOT 1
- Please release Babel 8 with features from v7.23.9 HOT 2
- [Bug]: Error: Can't resolve '@babel/runtime-corejs3/helpers/asyncToGenerator' HOT 1
- [Bug]: @babel/[email protected] breaks linting with legacy decorators HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from babel.