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

Make ts-loader compatible with node v6 #202

Merged
merged 1 commit into from
Aug 31, 2016

Conversation

Blechhirn
Copy link
Contributor

Node 6+ enforces the parameter to path.dirname to be a string (nodejs/node@08085c4). The empty string results in the previous behavior.

Node 6+ enforces the parameter to path.dirname to be a string (nodejs/node@08085c4). The empty string results in the previous behavior.
@johnnyreilly
Copy link
Member

I'll leave this to @jbrantly to merge but I wanted to be clear as to the problem this solves. Does ts-loader not work with node 6? I haven't tried it myself...

@Blechhirn
Copy link
Contributor Author

That's right - at least in my context where that config file parameter was not used.

@Blechhirn
Copy link
Contributor Author

I have been upgrading several web pack loaders in the last week after switching to node 6 in my projects. All of them had very similar issues. Btw: seems like some other user also reported this (last comment here: #115).

@jhchen
Copy link

jhchen commented Jun 7, 2016

I've been using ts-loader in quill and looks like node v6 with ts-loader is causing build errors. The code changes in this PR fixes the issue.

@johnnyreilly
Copy link
Member

I think we should merge this; it's minor and backwards compatible .@jbrantly are you happy with this?

@johnnyreilly johnnyreilly changed the title Don't call path.dirname with null/undefined Make ts-loader compatibly with node v6 Jun 30, 2016
@johnnyreilly johnnyreilly changed the title Make ts-loader compatibly with node v6 Make ts-loader compatible with node v6 Jun 30, 2016
@bezreyhan
Copy link

any update on this issue?

@johnnyreilly
Copy link
Member

Merged - sorry about the delay. I'm not sure when @jbrantly next hopes to publish but it'll be in the next release.

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

Successfully merging this pull request may close these issues.

4 participants