I'm using vim to write AppEngine code. There are two useful plugins that don't work well.
Syntastic: It shows the appengine imports as errors.
goimports (https://github.com/bradfitz/goimports): I've added an issue on that project as well with the same issue that it does not recognize appengine imports.
Is there a way to fix this?
thanks
The following (unofficial) appengine syntastic checker should work (automagically):
https://github.com/roktas/syntastic-more
P.S. For the reasons depicted in the relevant comment, this checker is a bit dirty hack and has not yet been submitted to the official Syntastic repo. Please use Github Issues for bugs.
Related
This is just for describing the issue and sharing my solution, I got stuck a lot of time on it.
This issue happened after I upgraded the Angular 10 -> 11 and changed the builder from udk:udk-runner to #angular-devkit
The issue I was facing is when I set the field bundleDependencies in angular.json to true . The Puppeteer cannot start with the error cannot launch the browser
Then I found it also happened on the other external libraries I'm using at the Server side like BullJS Bull-Board Puppeteer-Cluster with the below error
Github source for demo the issue: https://github.com/phattranky/angular-ssr-error-with-pupepteer
The solution is quite simple you just need to add externalDependencies below the field bundleDependencies, which are the libraries we are using.
"externalDependencies": ["puppeteer", "puppeteer-cluster", "bull", "bull-board"]
Sample:
What is the externalDependencies ?
https://github.com/angular/angular-cli/blob/master/packages/angular_devkit/build_angular/src/builders/server/schema.json
If you have the better solution and any feedbacks, please share for me. Thanks
I want to upload my project to Vercel but i have a problem with the build, i am new in this, so i don't know what to do, please help me, the first pic is the error that i have in Vercel
I experienced the same error. My solution was to delete one file (it wasn't currently in use). It was impeding the page from being built and, then, deployed. Check your '/', '/404' and '/Store' files. Try to look for any importations you may be missing, and also look for errors with any of your routes, if you're using them, those can be quite tricky.
Also, feel free to share the code in those 3 files aforementioned.
I'm trying to integrate the cwac-cam2 library with codenameone. The lib is in .aar format but when I build it fails whith the following error:
org.gradle.process.internal.ExecException: Process 'command '/home/ec2-user/android-sdk/build-tools/23.0.1/aapt'' finished with non-zero exit value 1
I can not find out what is wrong. Can you help me please?
Lib reference: https://github.com/commonsguy/cwac-cam2
Its a bit difficult for me to say what exactly wrong is, but you can try some general steps that I would follow like
1) Check your .aar lib is residing at appropriate location. Normally for Android it will be at ..\YourProject\native\android\YourLib.aar
(also do 'Refresh cn1lib files' once, because I did so.. lol)
2) check build hint and make sure you have
android.enableProguard = false
3) If you are using any activity from that .aar lib then make sure you have added those activity/ies in build hint as android.xapplication = <activity android:name="com.XX.YY.MyActivity" />
I would further suggest you look at Chen's post on ARR integration here: http://www.codenameone.com/blog/integrating-android-3rd-party-libraries-jni.html
Also notice that gradle builds are often harder to work with in terms of result readability. I would suggest trying to disable gradle first and getting it to work without it then re-enabling it so you can test with android studio if necessary. You can disable gradle with the build hint android.gradle=false.
Installed Google Dart 1.0. Basically a Dart noob at this point...
angular.dart tutorial apps at - https://github.com/angular/angular.dart.tutorial
Seems broken or I am doing something wrong.
in chapter folders, file pubspec.yaml contains text: ../pubspec.yaml - which seems to be non yaml.
pub errors out with
Pub get failed, [1] Error in pubspec.yaml: The pubspec must be a YAML mapping.
There is a common pubspec.yaml in dir below chapter dirs, it contains legit yaml.
Even after editing chapter project pubspec.yaml with "common" pubspec legit yaml content and doing pub get, chapter 03..06 demos have missing package references.
Anyone who can tell me what I'm doing wrong appreciated.
There is a bug with the tutorial on Windows: https://github.com/angular/angular.dart.tutorial/issues/8
which should be fixed soon.
Having the same issue at present.
Short-term solution appears to not be to edit yaml files/links, (if you have, its probably best to re-download the tutorial files from fresh)
instead:
open the main.dart files in each affected example,
changes lines such as:
import 'package:angular_dart_demo/rating/rating_component.dart';
to
import '../lib/rating/rating_component.dart';
(you should see the ~ underlines disappear when you type this)
I think this has been due to some recent restructuring of the example files, since these were working until recently.
My question:
From the readme on https://github.com/yeoman/generator-angular
yo angular:controller user
Produces
app/scripts/controllers/user.js
How do I make it produce
app/js/controllers/user.js
What I've looked at:
I don't think I can configure the path since the source shows that the path is hard codded:
Generator.prototype.createControllerFiles = function createControllerFiles() {
this.appTemplate('controller', 'scripts/controllers/' + this.name);
this.testTemplate('spec/controller', 'controllers/' + this.name);
this.addScriptToIndex('controllers/' + this.name);
};
https://github.com/yeoman/generator-angular/blob/master/controller/index.js#L22
I've considered forking the project and changing the code, but that feels dirty.
I'm hoping that there is a configuration i can change, but there is no github wiki, so I can't exactly RTM to find the configuration options. I tried looking in https://github.com/yeoman/generator-angular/blob/master/script-base.js but that wasn't very helpful either.
Unfortunately there is no fix for this right now.
But the good news is that the team is working on a solution for this. See this Twitter conversation.