Comments (8)
Changing to spec issue. The new compiler supports merging of all module declarations, including ambient external module declarations. I see no reason why we should only allow merging of internal modules and specifically disallow merging of ambient external modules. In particular, declaration files sometimes extend existing internal modules and may want to do exactly that for ambient external modules.
from typescript.
From design meeting: agreed this should merge just like internal modules.
from typescript.
Leaving open so we can make the text change to the spec
from typescript.
When I run this code in typescript I get
ldixon/foo.ts(4,16): error TS2000: Duplicate identifier '"fs"'. Additional locations:
ldixon/foo.ts(1,16)
ldixon/foo.ts(4,16): error TS2191: Ambient external module declaration cannot be reopened.
Sounds like the correct behaviour is no errors. Would be great to have an npm publish of a version with this fixed :)
from typescript.
agreed this should merge just like internal modules.
DT actually needs this. Thanks guys (/cc @Bartvds @vvakame will possibly make non-instantiated modules less necessary)
from typescript.
It seems like this doesn't work if the module is exported by assignment?
declare module "m" {
function inner(s: string);
module inner { export interface Test {t: string;} }
export = inner //error here
}
declare module "m" {
// even though we're only extending already existing submodule
module inner { export interface Other { t: number; } }
}
from typescript.
@spion The name inner
is not "shared" between declarations here -- when there's an export =
, all other declarations inside that module declaration are considered to not be visible at all
from typescript.
@RyanCavanaugh I see. The original problem is express.d.ts
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/express/express.d.ts
Here, express exposes a namespace Express
to let us extend Request
. Unfortunately those extensions cannot contain types imported from ambient external modules, which means they're of limited use. However, since express-the-module is also a function, the only way to declare the module is to use declaration merging then write export = module at the end, so we can't use declaration merging for ambient external modules either.
I'll open a separate issue.
from typescript.
Related Issues (20)
- variable incorrectly typed as true instead of boolean when change is made inside IIFE HOT 1
- Add a rule to the compiler options to disallow the `assert` keyword for import attributes HOT 1
- Code reachability contains False Positive in simple "always true" return condition HOT 7
- Type printing does not detect that a name is shadowed in the current scope
- Add generic to AggregateError HOT 1
- A function with a return type of void can't be awaited without a warning HOT 7
- Design Meeting Notes, 5/7/2024
- `window.parent` should be nullable HOT 6
- Class field does not apply control statement correctly when using it inside a function HOT 1
- Additions result wrong HOT 5
- Incorrect type inference in class implementation of interface with method Accepting partial type HOT 4
- `.call` on an union with different arguments counts fails when passing `any` HOT 2
- TS returns an absurd type when using an inherited getter (I guess there is some kind of cache issue or something ???) HOT 1
- Inconsistency in Generic Inference for Private Properties HOT 4
- Should changing the method name from full-width characters ("fA") to half-width characters ("fA")
- 5.5.0 regression - Named exports of functions are not emitted for CommonJS HOT 4
- The inferred type of 'actions' cannot be named without a reference to '../../.yarn/__virtual__/@reduxjs-toolkit-virtual-5ff160901c/4/.yarn/berry/cache/@reduxjs-toolkit-npm-2.2.3-3fa8bcc11c-10c0.zip/node_modules/@reduxjs/toolkit/dist/entities/models'. This is likely not portable. A type annotation is necessary. HOT 4
- Different behavior between const and readonly for multidimensional array access/strict null checking HOT 6
- Rename symbol weirdness with typescript type properties
- object getters return type error HOT 12
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 typescript.