I have updated my Angular CLI, with version 10.0.5 (globally and locally both) And while I am trying to build my angular project by below command-
ng build
I am getting below error-
Schema validation failed with the following errors: Data path ""
should NOT have additional properties(es5BrowserSupport).
While I explored this error I found that-
#angular/cli required minimum version 7.3 &
#angular-devkit/build-angular required minimum version 0.13
But I think I have the updated versions because I re-checked and it was showing I already have the updated versions of both the packages.
FYI..I can't comment this option (es5BrowserSupport : true) in Angular.json, I want to keep this because if I comment this option it's giving other issues.
Now I am not understanding what I am doing wrong here. Can anyone suggest some way to resolve this? Because currently I am unable to run my project because of this issue.
FYI, my old Angular CLI version was-
#angular/cli": "^8.3.20"
The property es5BrowserSupport was deprecated and has been removed.
The inclusion for ES5 polyfills will be determined from the browsers listed in the browserslist configuration.
BREAKING CHANGE
Deprecated browser builder option es5BrowserSupport has been removed. The inclusion for ES5 polyfills will be determined from the browsers listed in the browserslist configuration.
https://github.com/angular/angular-cli/pull/17484
Related
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.
I recently upgraded my project from Angular 11 to Angular 12.
Now, I am trying to enable IE 11. Did following:
Did the polyfills.ts file changes
pointed tsconfig.js to es5
removed not from IE 11 entry int .browserslistrc
Now I am not able to ng serve.
It crashes with following error:
Unknown error from PostCSS plugin. Your current PostCSS version is 8.3.6, but
postcss-preset-env uses 7.0.39. Perhaps this is the source of the error below.
I tried following to resolve this:
deleted node_modules, package-lock.json and did npm i several times - didn't work, same issue on ng serve
upgraded npm 6 to npm 7, added .npmrc with legacy-peer-deps=true - didn't work, same issue
used yarn to install the packages - didn't work same issue
added postcss, postcss-preset-env packages directly to depedencies - didn't work, same issue
added postcss, postcss-preset-env packages directly to devDepedencies - didn't work, same issue
I am using node 14.
Only thing that works is if I put the not back in front of IE in .browserslistrc, which was the whole point of doing this exercise.
Does anyone have any clue on how I might solve this?
I have a Gatsby starter (taylorbryant/gatsby-starter-tailwind) that uses gatsby-plugin-postcss which is not compatible with the version of gatsby installed in my machine like a few other plugins used in the starter. You can see the warning I get when trying to build for production.
warn Plugin gatsby-plugin-postcss is not compatible with your gatsby version 3.14.2 - It requires gatsby#^2.0.0
How can I downgrade Gatsby to a specific version, maybe just locally?
This isn't too difficult.
Open your package.json file and change the actual version you want to use.
Then run npm update to make sure you update all the packages to the right version.
Please correct me if I'm wrong but I believe that is the way to change the Gatsby version.
Please do keep in mind that this is most probably cause a bunch of other discrepancies with other packages that actually require a higher version in order to work.
You can find more information about how different versions work here: https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/
Best of luck!
We have a private nexus repository and publishing all the npm modules there. We have Module A and Module B, B is dependent on A. Here I am getting an issue with installing the latest SNAPSHOT version. For example:
Module A has published versions like
'1.0.0-SNAPSHOT', '1.0.1-SNAPSHOT', and '1.0.0'
In Module B package.json, I added the dependency like
"Module A": "^1.0.0-SNAPSHOT"
As I mentioned "^" in the dependency, it should install the latest version (i.e, 1.0.1-SNAPSHOT), But I am not sure why it is installing '1.0.0' instead '1.0.1-SNAPSHOT.
Your help would be greatly appreciated. Thanks in Advance.
Avoid releasing and using snapshot dependencies. When you publish a release, it should not contain -SNAPSHOT. Referring to a proper release is mandatory in order to be sure you are testing/executing the right code without side effects due to regression problems. You need to know in every moment which version you are using, that is very important, so relying on latest versions of your modules might not be the best solution, it doesn't worth it either if you are precise with major, minor and patch bits in order to avoid breaking changes or unexpected behaviors.
If you really need to develop them together you can use npm link command instead.
The online NPM documentation does not explain how to upgrade ember-cli-babel. I tried following the accepted answer posted here Invalid Version: Ember-Cli-Babel, but that did not work.
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade
to at least ember-cli-babel 6.6. Version 5.2.8 located: library-ui ->
ember-clean-tmp -> ember-cli-babel
Update
I have uninstalled the Ember-clean-tmp add-on. When I run Ember-cli-update I get a message that says Tags match, nothing to apply. I then ran Ember S and get the following warnings:
WARNING: ember-basic-dropdown attempted to include external babel
helpers to make your build size smaller, but your root app's
ember-cli-babel version is not high enough. Please update
ember-cli-babel to v7.3.0-beta.1 or later.
WARNING: ember-power-select attempted to include external babel
helpers to make your build size smaller, but your root app's
ember-cli-babel version is not high enough. Please update
ember-cli-babel to v7.3.0-beta.1 or later.
WARNING: ember-data attempted to include external babel helpers to
make your build size smaller, but your root app's ember-cli-babel
version is not high enough. Please update ember-cli-babel to
v7.3.0-beta.1 or later.
WARNING: ember-basic-dropdown attempted to include external babel
helpers to make your build size smaller, but your root app's
ember-cli-babel version is not high enough. Please update
ember-cli-babel to v7.3.0-beta.1 or later.
WARNING: ember-text-measurer attempted to include external babel
helpers to make your build size smaller, but your root app's
ember-cli-babel version is not high enough. Please update
ember-cli-babel to v7.3.0-beta.1 or later.
WARNING: ember-power-select attempted to include external babel
helpers to make your build size smaller, but your root app's
ember-cli-babel version is not high enough. Please update
ember-cli-babel to v7.3.0-beta.1 or later.
Update 2
I was able to fix the issue by uninstalling ember-cli-babel and re-installing it, which got me to version 7.5.0. But, is this the correct way to upgrade packages?
The problem that you are experiencing is related to one of your addon's depending on an older version of ember-cli-babel.
From the deprecation notice, it's ember-clean-tmp, which doesn't look to be up to date. You have a number of options here. First, you could stop using the addon (which in this case doesn't really seem like a necessary addon. Needing to clear my tmp has never been a problem for me in my 2.18 app).
Secondly, if you'd like to keep using the addon, you could go through the process of upgrading the addon's ember-cli version to a version that includes a high enough ember-cli-babel version. Basically, each ember-cli version has a default blueprint for what dependencies a new app should include. When you ugprade, you diff your dependencies and various files against the default for that ember-cli version. ember-cli-update is an addon that makes this process nice. You can then point at your own fork or better yet, get your update merged upstream in ember-clean-tmp
Open you Command Prompt and type ember install ember-cli-babel and press enter. If you have already installed, don't worry. This will over write.
Reference: https://www.npmjs.com/package/ember-cli-babel
First,
npm install ember-svg-jar
Second,
ember install ember-svg-jar
All I had to do were these commands.