-
Notifications
You must be signed in to change notification settings - Fork 307
Ionic serve watch does not output Typescript errors #1355
Comments
you know that this issue is major urgent, why ? |
+1 here. I expect ionic serve to act similar to ng build --watch. |
This issue is very serious, it's curious that less people are here. Wondering if it's something specific to a certain setup. I am facing this too:
|
Also, as of v4 Ionic are moving to ng-cli anyway, so this will be moot: However I really need a workaround in the interim. |
Have a fix working for this against In var host = compiler_host_factory_1.getInMemoryCompilerHostInstance(tsConfig.options);
if (workerConfig.useTransforms && helpers_1.getBooleanPropertyValue(Constants.ENV_PARSE_DEEPLINKS)) {
// beforeArray.push(purgeDeepLinkDecoratorTSTransform());
// beforeArray.push(getInjectDeepLinkConfigTypescriptTransform());
// temporarily copy the files to a new location
copyOriginalSourceFiles(context.fileCache);
// okay, purge the deep link files NOT using a transform
var deepLinkFiles = util_1.filterTypescriptFilesForDeepLinks(context.fileCache);
deepLinkFiles.forEach(function (file) {
file.content = util_1.purgeDeepLinkDecorator(file.content);
});
var file = context.fileCache.get(helpers_1.getStringPropertyValue(Constants.ENV_APP_NG_MODULE_PATH));
var hasExisting = util_1.hasExistingDeepLinkConfig(file.path, file.content);
if (!hasExisting) {
var deepLinkString = util_1.convertDeepLinkConfigEntriesToString(helpers_1.getParsedDeepLinkConfig());
file.content = util_1.getUpdatedAppNgModuleContentWithDeepLinkConfig(file.path, file.content, deepLinkString);
}
} with var host = ts.createCompilerHost(tsConfig.options); remove / comment: resetSourceFiles(context.fileCache); As per: https://gist.github.com/lathonez/672609416bac268f07ead769763cecaa#file-transpile-js-L125-L152 That gist is a working copy of |
Is there any news regarding this issue? it's a pain having to either monkey patch or manually change using the fix by @lathonez (which does work, YMMV!) Edit: I'm using 3.1.8 |
I still have this issue too. So annoying.. I use version 3.20. I'm afraid to mess with webpack to be honest. I'll try the workaround. Thanks EDIT also, since it looks related, I sometime have the serve script complaining about error AFTER I FIXED THEM. It sometime look like it's caching my code for a while and it's randomly reloaded. It's weird. |
Bump. This issue is very very very annoying!!! |
Delicious issue that makes development a great pain |
Same here, please fix! |
after on year it is still not working. I'm really pissed. Ionic people are only concerned about the next version or something. I mean how can you folks develop, when the errors are not shown ?!?!?!?!?! |
moving to ionic v4 is not an option for me, i have a big app with ionic 3 and it works fine, but developing without seeing the errors is impossible. |
With your fix laze loading the ionic-pages does not work anymore :( |
umm this sounds rather serious, any plans to address this? |
Note: for support questions, please use one of these channels:
https://forum.ionicframework.com/
http://ionicworldwide.herokuapp.com/
Short description of the problem:
When using ionic serve it only shows Typescript errors the first run of build
after that when the watch triggers, it says "build finished" although there are typescript errors...
What behavior are you expecting?
Ionic serve should also fail the build and show Typescript errors when in watch mode
Steps to reproduce:
Which @ionic/app-scripts version are you using?
3.1.6
Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
The text was updated successfully, but these errors were encountered: