-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
Ignore option throwing errors #265
Comments
larsgw
added a commit
to larsgw/babelify
that referenced
this issue
Apr 29, 2018
This may be the case if files are ignored. I do not know what the other cases are, and if they should be handled differently, but at least they don't cause error like this. See babel#265
This was referenced Apr 29, 2018
larsgw
added a commit
to larsgw/babelify
that referenced
this issue
Apr 29, 2018
This may be the case if files are ignored. I do not know what the other cases are, and if they should be handled differently, but at least they don't cause error like this. See babel#265
larsgw
added a commit
to larsgw/citation.js
that referenced
this issue
Apr 30, 2018
expect.js doesn't play nicely with Babel, so it shouldn't be transformed by Babelify.^1 Note that the ignore option in Babelify is buggy ^2, so this might not work on your end. ^1 Automattic/expect.js#149 ^2 babel/babelify#265
larsgw
added a commit
to larsgw/citation.js
that referenced
this issue
May 2, 2018
* [site:test] Fix browser tests again expect.js doesn't play nicely with Babel, so it shouldn't be transformed by Babelify.^1 Note that the ignore option in Babelify is buggy ^2, so this might not work on your end. ^1 Automattic/expect.js#149 ^2 babel/babelify#265 * [test:input] Set up HTTP request mocking Set up proper HTTP request mocking by mocking exports with mock-require. Not possible in the browser, but it wasn't before, so this counts as an improvement. Previously done by nock, but this didn't work for requests made through sync-request, as that spawns a child process over which nock has no control. See #68 See 509d911 Close #134 * [test:input] Increase coverage of input plugins See #123 * [package] Add non-npm patch to dependencies See babel/babelify#267
loganfsmyth
pushed a commit
that referenced
this issue
Sep 3, 2018
This may be the case if files are ignored. I do not know what the other cases are, and if they should be handled differently, but at least they don't cause error like this. See #265
Fixed in #267 |
larsgw
added a commit
to citation-js/citation-js
that referenced
this issue
Nov 24, 2018
* [site:test] Fix browser tests again expect.js doesn't play nicely with Babel, so it shouldn't be transformed by Babelify.^1 Note that the ignore option in Babelify is buggy ^2, so this might not work on your end. ^1 Automattic/expect.js#149 ^2 babel/babelify#265 * [test:input] Set up HTTP request mocking Set up proper HTTP request mocking by mocking exports with mock-require. Not possible in the browser, but it wasn't before, so this counts as an improvement. Previously done by nock, but this didn't work for requests made through sync-request, as that spawns a child process over which nock has no control. See #68 See 509d911836c7cb7adbc57440ce21a703308e01ff Close #134 * [test:input] Increase coverage of input plugins See #123 * [package] Add non-npm patch to dependencies See babel/babelify#267
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using the
ignore
option results in the following error:Using the following babelify options:
Source (AFAICT)
Caused by this, due to
result
being null:babelify/index.js
Line 31 in c5e4d40
This happens on ignored files, as expected. My guess is that that happens because of
in
@babel/core
.This causes
loadPrivatePartialConfig
to returnnull
loadFullConfig
to returnnull
loadConfig
to returnnull
transform
to returnnull
Full options:
The text was updated successfully, but these errors were encountered: