Skip to content

fix: pass appPath to the env from karma.conf.js #5071

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

Merged
merged 1 commit into from
Oct 14, 2019
Merged

Conversation

Fatme
Copy link
Contributor

@Fatme Fatme commented Oct 14, 2019

Two different webpack compilations are started on tns test command - the one from karma-webpack and the second one from nativescript-dev-webpack. As the karma's webpack doesn't provide appPath to the env and there is a hardcoded appPath inside webpack.config.js (to src for example), it works only with that hardcoded path.

Rel to: #5070

PR Checklist

What is the current behavior?

What is the new behavior?

Fixes/Implements/Closes #[Issue Number].

@cla-bot cla-bot bot added the cla: yes label Oct 14, 2019
Two different webpack compilations are started on `tns test` command - the one from `karma-webpack` and the second one from `nativescript-dev-webpack`. As the karma's webpack doesn't provide appPath to the env and there is a hardcoded `appPath` inside `webpack.config.js` (to `src` for example), it works only with that hardcoded path.

Rel to: #5070
@Fatme Fatme force-pushed the fatme/fix-unit-testing branch from 1f2231c to a54ba74 Compare October 14, 2019 06:34
@Fatme
Copy link
Contributor Author

Fatme commented Oct 14, 2019

test cli-tests

@Fatme Fatme merged commit 0c79359 into master Oct 14, 2019
@Fatme Fatme deleted the fatme/fix-unit-testing branch October 14, 2019 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants