question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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 use storybookBuildDir to upload the prebuilt Storybook.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:3
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

4reactions
jmhobbscommented, May 19, 2021

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 }}
0reactions
ghengeveldcommented, May 19, 2021

This should be fixed with chromatic@5.8.2. Please let us know if it doesn’t resolve the problem for you.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Node.js - endoflife.date
Release Released Active Support Se... 19 2 months and 1 week ago. (18 Oct 2022) Ends in 3 months. (01 Apr 2023) En... 18 (...
Read more >
Community support for Node 14 LTS is ending on 30 April 2023
On 30 April 2023, extended support for Node 14 LTS will end. After that date, your applications that are hosted on App Service...
Read more >
Node.js ES2015/ES6, ES2016 and ES2017 support
Yes. Yes Yes. Yes Error. Error Error. Error Error. Error Error. Error function() function() function() function() function() function() function() function() function() function() function() function() function() function()...
Read more >
Supported Node versions - Node-RED
Supported Node versions. Node-RED currently recommends Node 16.x LTS. Version, Support Level, Notes. < 10.
Read more >
How to fix 'npm does not support Node.js v14' error on ...
How to fix 'npm does not support Node.js v14' error on Windows 10 · Uninstall node.js (Windows Add/Remove programs) · Manually delete the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found