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
Support Node 14 #346
Comments
This can also cause issues for compiled packages and bindings, for example node-sass, resulting in errors like:
This class of errors can be worked around by using the setup-node action and using Node 12 in the |
Hello @jmhobbs , We got the same issue on our ends, would you mind sharing you work around in this thread please? Thanks in advance |
For the issue with compiled packages, not missing language features, the action file would look something like this: name: 'Chromatic'
on: push
jobs:
chromatic-deployment:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
############################################
# Insert this step before npm / yarn install
- uses: actions/setup-node@v2
with:
node-version: '12'
############################################
- name: Install dependencies
run: yarn
- name: Publish to Chromatic
uses: chromaui/action@v1
with:
token: ${{ secrets.GITHUB_TOKEN }}
projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }} |
That is working, many thanks @jmhobbs |
For me above node-version setting does not work, as package.json has the following engine configuration
it would be great if you can support node v14 |
This should be fixed with |
Some features, like optional chaining, are unsupported in Node 12. This can be problematic because GitHub actions supports Node 14 (14.16.1 at time of writing), leading to a split where
run
steps are in Node 14, but our action is running on Node 12.Generally this is not an issue, but can be confusing because a Storybook build will work in a
run
step, then fail when invoked by the action.This update is blocked by actions/runner#772, as JavaScript actions do not currently support
node14
.The current workaround is to build in a
run
step to a known directory, then usestorybookBuildDir
to upload the prebuilt Storybook.The text was updated successfully, but these errors were encountered: