Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,558,752
Community Members
 
Community Events
184
Community Groups

Old Pipeline, Used for a Few Years - Now Failing

Christian Griffith
Christian Griffith May 19, 2023

We use Bitbucket to manage and compile our main SASS repo. The pipeline in question is very basic and uses Node and SASS to compile and compress CSS for the front-end (also generates a source map file for debugging).

I setup the pipeline YAML  a few years back, and it's worked fine for a good while. Now, today, when trying to run the pipeline, it fails when it reaches the following line:

sass --style=compressed --embed-sources sass/styles-main.scss compiled-www-stylesheet/styles-main.css

Error Message: ReferenceError: globalThis is not defined...

I appreciate any/all suggestions!!!

Answer
Watch
Like Be the first to like this
96 views

1 answer

0 votes
Christian Griffith
Christian Griffith May 19, 2023

I think I've got it fixed—updated the "image" line of the pipeline to:  image: atlassian/default-image:3 

We were using default-image:2 before...

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events

See all events