facing error while stencil bundle command - bigcommerce

currently i update my node and npm version for stencil bigcommerce when i make bundle for my old project i'm facing this type of problem. can anyone solve my this issue?
Error: No input specified: provide a file name or a source string to process
---------WARNING---------
We are currently in the process of deprecating node-sass fork https://github.com/bigcommerce-labs/node-sass
Your scss files were compiled using latest node-sass version https://github.com/sass/node-sass
This error might indicate that your scss file is not compatible with it.
There is still an option to compile scss file old fork by using --use-old-node-sass-fork.
But note, that this will lead to 500 error in production in near future.
---------WARNING---------

The best solution would be to resolve the SCSS errors in your files that are causing a failure.
However, a quick solution may be to roll back your stencil version. Try npm install -g #bigcommerce/stencil-cli#3.12 and then try bundling your theme. Note: you will need to be on Node v12 for this.

I solved this error, their were no node or big commerce CLI version issue, I had to just upgrade my bootstrap version in Base.html file and the error was solved.

Related

Error in emotion/styled package, cannot find answer ANYWHERE

I keep getting the following error, I'm using meteor 2.1 currently
Error: A new entrypoint in the #emotion/styled package, #emotion/styled/base, has replaced the #emotion/styled-base package. Please remove this package and use #emotion/styled/base instead.
i cannot find ANY way to install this #emotion/styled/base package. #emotion/styled-base is installed and i cannot create a build suddenly.
any suggestions???
I'm using react.js
#emotion/styled/base isn't a package you need to install, but rather its a submodule of the #emotion/styled package.
I have a hunch that you are not using #emotion/styled-base directly, so most likely what you have is a version mismatch where you have a newer version of #emotion/styled installed, but that package is written for an older version. You'll probably just need to locate this offending package and update it.
If this isn't the case, then you'll just need to replace your imports for #emotion/styled-base with ones for #emotion/styled/base

Vue packages version mismatch on Nuxt.js

I'm trying to upgrade from Vue 2 version to vue 3, my project has Nuxt.js framework.
I put this command to upgrade : vue add vue-next, and upgrade has been successful. but when I try to execute project appear the next error :
Vue packages version mismatch:
- vue#3.0.7
- vue-server-renderer#2.6.12
This may cause things to work incorrectly. Make sure to use the same version for both.
I don't know how to resolve this problem.
That problem happened to me after an update. This is what worked for me.
delete the project's node_modules folder
delete the package-lock.json file
npm i
Solution found here https://github.com/nuxt/nuxt.js/issues/6823
see post from "daniplaninc"
The problem you are mentioning here comes from the fact that Nuxt 3 hasn't been released yet : it still doesn't support Vue 3, hence your application won't compile with vue 3...
The release is planned for Midsummer 2022 : https://v3.nuxtjs.org/community/roadmap/
I am waiting for this version too so I hope it will be released soon !

GatsbyJS - Can't resolve 'babel-runtime/helpers/possibleConstructorReturn'

I have a website that has been running fine for the last 4 months. Randomly the site stopped deploying on Netlify and I keep getting this error:
Generating development JavaScript bundle failed
Can't resolve 'babel-runtime/helpers/possibleConstructorReturn' in
'D:\Websites\nemesis-cheer\node_modules\react-script-tag\lib'
I have tried reinstalling babel, tried downgrading to different versions of babel/runtime, tried clearing cache and redeploying, Even tried reverting to old versions of the repo that I know for a fact deploy successfully and they still failed.
Here is my deploy log:
https://pastebin.com/raw/dH45EtP5
The repo is:
https://github.com/mont266/nemesis-cheerleading
Im really stomped here if anyone could help me out I would really appreciate it.
Try upgrading your babel/core dependency.
Now you have it locked to 7.13.8 (according to your package-lock.json), and it seems that the missing helpers are fixed in the 7.5.5, according to this stack trace.
I fixed the issue by reinstalling yarn and doing 'yarn add babel-runtime'. Must've gotten rid of the entire plugin at somepoint by accident.
I suggest you to try adding "babel-runtime": "6.26.0" to your package.json
Maybe it would fix an error for you

Drizzle installation end up with errors

I have followed the this tutorial from Truffle official page, First few steps goes smoothly and when i tried to install drizzle on client directory as per the tutorial says it ended up with this error message,
before this error message it has error with typescript package so i installed it manually, and this one is with scrypt.
previously it was about VS build tools, now it is with Scrypt package, with missing some files.
Any suggestions.
Problem solved, it seems scrypt package supports node 11v only.

React Native Build Error for Android after Gradle Upgrade

What went wrong:
A problem occurred configuring project ':app'.
Could not generate a proxy class for class com.android.build.gradle.tasks.BuildArtifactReportTask.
I got the same problem and solved it by update my JDK version from 1.8.0_20 to 1.8.0_171. You may try update your JDK version as well.
This is want I did to followed to fix.
I had already updated java.
But the important thing is to update JAVA_HOME variable which react-native-cli checks when executing its build process. I have had the latest 1.8.0_191 update but still the build failed.
So this is how I solved it. By making sure my react-native-cli refers to latest JDK by means of env variable.
I had your same problem, I had JDK 1.8.05 and upgrade to 1.8.0_172, delete your .gradle folder of the project, and run again react-native run-android.. have fun