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

Typescript errors handler #254

Open
giolf opened this issue Aug 19, 2018 · 4 comments
Open

Typescript errors handler #254

giolf opened this issue Aug 19, 2018 · 4 comments
Assignees

Comments

@giolf
Copy link

giolf commented Aug 19, 2018

I've just a simple question:
In my Angular project all my files are .ts.

If there are some errors on my files, during build time In the Log area they are partially correct:
The file name is correctly highlighted but the row and column number is wrong, in fact for each error i get this sentence:
You may need an appropriate loader to handle this file type

There is a way to use the same error style for typescript files ?

thank you

@ryan-roemer
Copy link
Member

@giolf -- Can you open up a minimal repository with a dummy TS file and a full webpack config with install + error reproduction steps so that we can clone down the whole thing and see for ourselves what you're seeing? Thanks!!!

@parkerziegler
Copy link
Contributor

@giolf Typically I see that error if I don't have a proper loader for TS files configured in my webpack setup. What loader are you using for your TS files to compile them to JS? We'll take a look on our end, but can you ensure you're using a properly configured loader like ts-loader. webpack has a great guide for this setup here.

@giolf
Copy link
Author

giolf commented Sep 24, 2018

Hey guys, I’m sorry if I’m answering just now but I had a veeeery stressfull time.

I’m using the angular cli (angular 6) which with some tricks allow to customize the webpack.conf file. Unfortunately I didn’t have time to investigate anymore about this issue. But in the next days I will write here more details about my current setup.

Thx in advance

@ryan-roemer
Copy link
Member

@giolf Thanks. Anything we can clone and immediately see the problem on our machines will ensure we have as rapid response as possible (or CodeSandbox too!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants