-
Notifications
You must be signed in to change notification settings - Fork 188
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
Zipping projects and dependencies
does not like certain tokens/features of more recent Node versions
#614
Comments
@newhouse! Thank you for taking the time to report this issue and for including such a detailed description! I'll be taking a look at this issue and will report back here once we have a fix in place. |
@rnegron Thanks!!! After poking around a bit I don't have high hopes for this getting fixed in browserify, and as time goes on their problem with modern syntax will become your Users' problems with modern syntax. You may want to consider another bundler? I don't have any to suggest and I know that's not a simple change, but it may be the only way. Perhaps another option might be to have a temporary babel transpilation step in your bundling and dependency stuff that targets something like Node 14 or whatever is the most accommodating for the shortcomings of browserify. But I would think you would not want to actually upload the transpiled code or you'd have all sorts of drawbacks like: source code mapping in errors, lack of native, non-transpiled efficiency and optimizations, things that cannot be transpiled (top level await?), etc. Just thoughts. Thanks for working on this! |
Hello @newhouse, wanted to give you a quick update on where we are on this issue. After determining that this is mainly related to the logical assignment operators introduced in Node.js v15, and seeing as there is potential for this to get fixed upstream, we have de-prioritized this issue for the moment. As I know you're aware, a temporary workaround around this is to set up a transpilation pipeline using I left a message in the open PR (browserify/detective#85 (comment)) that would unblock this, and will keep an eye out for opportunities to prioritize this fix in the Zapier CLI. |
Thanks for the update @rnegron! |
Confirming that this issue is also affecting private method/field symbols, ie:
I'm running into this issue with the The parser fails on reading private methods and fields due to reaching the "#" symbol and erroring out:
|
Bug Description
I have updated to version
13
of both Zapier Core and CLI. That version states that it will run on Node16
, so:As a result, now in my transpiled code I have a
nullish coalescing assignment
, which is a language feature that was added in Node 15 according to MDN.Yet, when I run
zapier build
, it will complain about anUnexpected token
It seems to me like
module-deps
needs to be able to understand and allow Node 16, etc, syntax? This syntax is OK in Node 16 for sure.Reproduction Steps
nullish coalescing assignment
into your code somewherezapier build
.Version Info
The text was updated successfully, but these errors were encountered: