There is a need in my project to have es2015 bundle. The v27 worked fine but updating it to v28 broke bundle work in ie11.
What is the possible reason and maybe what is the right polyfill to fix this issue?
Related
My project was created several years ago, and it's use babel 6.x.
Now, I need to import a plugin that depend on babel 7.x , and I try to use it, and didn't find problems yet, but I know it's a dangerous action to keep two different mainly babel version in one project.
And it will make a big influence if I upgrade the babel version from 6.x to 7.x, I guess I have no time to do it. So can I both use babel 6 and 7 in my project, and can anyone told me the risk of it?
I'm using Android Studio 3.0 (updated to canary 4 today) on macOS for a side project and recently (not sure really when) the constraint layout editor stopped working properly.
Now it just shows a grey window and the blueprint view isn't working at all. Even the properties editor on the right doesn't show the constraints anymore.
Here how it looks for a simple layout with just 1 button:
I'm using constraint layout 1.0.2 but it fails the same way on 1.1.0-beta1.
Any idea what could go wrong? No error are shown in the IDE or in the idea.log
Thanks in advance for any help provided :)
Which gradle version are you using? Also, support lib 26.0.0-beta2 has an issue with studio, if you are using it you should downgrade to beta1 to use the editor.
Just change the "Apptheme" to "AppCombat.NoActionBar"
downgrading it to beta1 solved my problem
Go in build.gradle and change the dependencies to 26.0.0-beta1:
After Sync the project...
Its works to me!!!!
What worked for me was to UPGRADE all my dependencies to the latest version (currently 27.0.0) instead of doing a downgrade. It brings some additional effort to replace the "compile" dependencies (which are deprecated) by "implementation" or "api" and upgrade also some of the libraries. But after all the upgrades the tool worked again perfectly.
Adding
implementation 'com.android.support.constraint:constraint-layout:1.1.2'
to the dependencies and reloading project solved my issue
Since Netbeans is used as my primary editor, and the project is built with angular-cli, this is a cosmetic issue, the project builds and deploys fine using ng serve -o, this is just an annoyance as I like my Netbeans to flag errors in files that actually have errors.
This is a Netbeans specific question, there are many "Cannot find module 'angular2/core'" questions but each requires different IDE configuration (VS, Webstorm, etc) I have not found one that addressed this issue in Netbeans.
To recreate the issue:
(using angular-cli)
ng new example-of-problem
Then opening example-of-problem in Netbeans:
As you can see from the above, a number of files have errors. All of which are resolving paths starting with '#angular' you can see it can resolve local paths fine (./app.component).
Some solutions request adding: "moduleResuolution":"node" to tsconfig.json however this is a standard angular-cli build and that line is of course present.
Versions of software:
Netbeans 8.1, Node 7.7.4, #angular/cli 1.0.0
The solution is to simply upgrade to netbeans 8.2. The typescript support has been fixed and the lines which are flagged above are no longer flagged.
Netbeans should automatically install the TypeScript Editor plugin, and as a matter of convenience install the netbeans-angular2-code-templates plugin.
I'm developing an eclipse plugin with a view. When launched in dev mode it's displaying and working perfectly fine:
But when I packaged and installed the plugin in the Eclipse instance, the view is empty when launched:
EDIT:
Looking at Error Log view, sometimes there is the following error:
org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: swing2swt/layout/BorderLayout
It might be relevant because a swing2swt.jar was magically automatically added to my plugin project by Eclipse. I tried including it in the build but the build failed complaining there is no value set for source.swing2swt.jar which I totally don't understand why it needs setting.
I have found the solution to this problem.
The problem itself is caused by swing2swt.jar not included in the build. For some reason WindowBuilder automatically added this jar to the project but didn't mark it for inclusion in the build.
However the struggle here is because Eclipse doesn't delete plugin jar files when uninstalling "software" that was previously installed. So if the version does not advance, the cached old, wrong plugin jar file will be reused when reinstalling the feature, causing any non-version-advancing fixes uneffective when reinstalling the feature/plugin.
It is so very common that during the development of a plugin, version does not advance for small fixes when trying distribution so I think this needs to be fixed. A ticket has been created at Eclipse site.
Bug 509781
Good morning:
I have a terrible problem with my Eclipse Juno.
Due to I had to format my computer, I lost the configuration of my Eclipse Juno.
I am trying to work again with my new Eclipse Juno configured, but I think something is missing.
My problem is, I import a Java Project that HAS NO ERROR some weeks ago, and I am 100 % sure about that.
Now, the project has errors like:
**The import javax.mail cannot be resolver
The import org.apache.commons.net cannot be resolved
TimeStamp cannot be resolver to a type
**
Of course, I tried all.
I cleaned the project.
I tried to remove and add again all the libraries I got in the java build path.
I tried to switch from jre6 to jre7.
I tried to change the Target Platform...
Nothing worked!! I am desperate!
Can anyone help me?
PS: I have the tomcat 5.5 installed in Eclipse Juno also.
Thank you.
Calm yourself. The problem is simply that your project need some additional libraries to be compiled. By the errors you showed, you need at least these:
javamail.jar
commons-net.jar
They are both open source libraries and you will find them with a bit of googling.
Why before formatting everything worked fine, and now it doesn't anymore? Surely you had these libraries in some other place outside your project. For example, within the bundled libraries of Tomcat.