stencil build throws error if component.d.ts is not present

[SebastianSchenk]

Stencil version:

 @stencil/[email protected]

I'm submitting a:

[x] bug report [ ] feature request [ ] support request => Please do not submit support requests here, use one of these channels: https://stencil-worldwide.herokuapp.com/ or https://forum.ionicframework.com/

Current behavior:

In our project we added src/components.d.ts to .gitignore, since we think that a auto generated file shouldn't be version controlled and could lead to unnecessary merge conflicts. Problem is that running the build script on a fresh checkout will throw the following error.

[ ERROR ]  Rollup: Unresolved Import
           Could not resolve './components' from src/index.js

After the error was thrown the src/components.d.ts file is generated anyway. So running the build script a second time will build the project correctly.

Expected behavior:

stencil build build should check for src/components.d.ts first. If not present, the file will be created. After creation the build should be executed.

Steps to reproduce:

• Create a new stencil component project
• Delete src/components.d.ts
• Run npm build

[manucorporat]

Creating component.d.ts is not that easy since it requires to transpile first everything. It's fixable, but a not trivial amount of work needs to be done. We might revisit it once we port to TS 3.6 (since we plan to use the new incremental apis). In the meantime, we recommend to commit that file.

[devinshoemaker]

is this now fixed? If I delete src/components.d.ts and then run npm run build then the file is regenerated. I'm using "@stencil/core": "^1.8.1" which has TypeScript 3.7 as a dependency.

[cremich]

@devinshoemaker I also observed this behaviour. But unfortunately the issue is still existing. It worked on my local machine but not on my CI pipeline. After some tests, I observed, that the build error appears if you

1. delete the node_modules
2. run an npm install following by a npm run-script build in a clean environment.

[ghost]

Confirmed the scenario mentioned by @cremich. Emptying the components.d.ts file is another way to replicate this issue.

[manucorporat]

Should not happen anymore since we released in the compiler update using latest TS!

[stevenbriscoeca]

@manucorporat Still doesn't work for me and I am using "@stencil/core": "^1.13.0",

Steps to reproduce :

• deleted the file, added to git ignore
• re-clone repo without file there
• run a build and it fails

[euxn23]

I found it had fixed in 1.14.0! @stephenbe

[SilverTracer]

@euxn23 , I'm on 1.17.3 version right now and this issue is still reproducible for me (in the same way as described in initial comment). @manucorporat , maybe some updates after fix broke this flow again?

[lorenwest]

@euxn23 , I'm on 1.17.3 version right now and this issue is still reproducible for me (in the same way as described in initial comment). @manucorporat , maybe some updates after fix broke this flow again?

Ditto - I've upgraded to stencil core v2.1.0 and can't get a clean build. Nothing listed in this thread seems to have fixed the issue for me. I have an external module, and this error happens when importing the external module.

[kassemsandarusi]

This still seems like an issue in v2.3.0. If I delete components.d.ts the first time I build it fails due the the error above. The second time it succeeds because the previous run generated components.d.ts.

[janrembold]

@manucorporat Could you please open this issue again. I can confirm the behavior in v2.5.2

[webdesign2be]

@manucorporat this issues is still present in version 2.6.0. I would appreciate a fix for this.

[kevin-coyle-pfizer]

I'm afraid I'm getting the same issue too on version 2.6.0

[tcarrio]

Seems this is still an issue in version 2.7.1

[adrianiy]

This still an issue in version 2.8.0 just FYI

[splitinfinities]

Hi all! Help us out. We need a reproduction case - specifically a GitHub repo that we can use to reproduce this behavior. If it is that you need to simply delete the definitions file in order to create this, that is good to know too. I'll reopen.

[littleninja]

The original comment includes steps to reproduce, is this sufficient?

Steps to reproduce:

Create a new stencil component project Delete src/components.d.ts Run npm build

[gtranter]

I have had success with the following workaround - add an empty index.ts file under src/components/. I'm using Stencil 1.12.7 and typescript 3.8.3.

[zovorap]

Any updates on this? None of the workarounds work for v 4.7.0

[gtranter]

Any updates on this? None of the workarounds work for v 4.7.0

I doubt this will ever be fixed since it was originally filed against Stencil v1. I would suggest you open a new issue against v4.7.0.

[rwaskiewicz]

Hey folks, please do not create a new issue in this case - this issue is tagged (with Bug Validated), ingested into our internal backlog, and has comments/additional information for the team there for when we get the chance to work on this. ATM, we still advise folks check this file into their source control, much like a package-lock.json file.

[zovorap]

While I'm personally ok with committing this file every time, But many devs around me always complain about it, since they often have to deal with merge conflicts. I think this is one of the things that retain people from starting using stencil on daily basis. I think it would be very beneficial for stencil if this can be fixed asap.