Closuer compiler having error like "namespace never provided' - ecmascript-6

I am compiling ES6 modules into ES3 via clouser compiler but getting error,
What am i doing wrong?
see this issue i've posted on github
https://github.com/google/closure-compiler/issues/2139

fixed is using **/*.js
(which cause all files be included in compiler)

Related

Fatal error (13): No program entry point with XDS Modula-2?

I'm using the current bundled binaries from https://github.com/excelsior-oss/xds (as of 12/6/2020) with just the most basic Hello World MOD file:
MODULE HelloWorld;
FROM STextIO IMPORT WriteLn, WriteString;
BEGIN
WriteString("Hello, World!");
WriteLn;
END HelloWorld.
xc HelloWorld.mod works fine for compiling it to object. However, I'm not clear on the exact syntax for xlink on a standalone MOD file. xlink HelloWorld.obj will at least get it to try with my object file, but as the error shows, it doesn't know the entrypoint. I've tried setting the entry point with the /ENTRY switch, but no luck doing it by module name. I've also tried setting the /SYS to console, but again, no luck there.
I feel there's some trivial linker option or program directive needed, but I'm just not finding it via Google...
To build a binary, use: xc =a =make HelloWorld.mod
The above is found in https://github.com/excelsior-oss/xds/blob/master/Sources/Doc/Comp/src/usage.tex .
It is unfortunate that XDS did not put PDFs of their documentation on github. I suggest building the documentation from their LaTeX files.
Edit: I since learnt that the Wayback Machine has archived the XDS documentation here: https://web.archive.org/web/20060705213825/http://www.excelsior-usa.com/xdsdoc.html

Babel helper-module-transforms runs into undefined is not a function

I am running mocha unit tests that are written in ES6. Using Babel to run the tests and running into a very bizarre error. This happens as soon as I import something from multiple test scripts. If ES6 Import is used from only one single test script everything works fine.
Here is a snippet of what the error looks like and I have a video that shows exactly how it can be reproduced.
/node_modules/#babel/helper-module-transforms/lib/normalize-and-load-metadata.js:37:52
TypeError: undefined is not a function
https://www.youtube.com/watch?v=jm0p1ttwFZc
Here is the git repo of the problem.
npm install
in /server
https://github.com/jiminssy/BabelProblem
This is because you are using https://www.npmjs.com/package/collections. It replaces many ES6-standard libraries with its own versions that do not conform to the standard behaviors that Babel is expecting and relies on to compile files.
Your option option would be to drop that library, or drop #babel/register. I'd recommend dropping the library since it seems to be extremely poorly designed.

Razor “The type or namespace name 'x' could not be found” Error. Compile Only

I have run into an issue with my razor templates.
In the the template I am using it has two using references at the top of the file.
#using Framework;
#using Bundler;
Both of these reference internal namespaces in my project that are both included as refs in the project that is compiling the template. However the bundler reference fails with the classic.
Unable to compile template. The type or namespace name 'Bundler' could not be found (are you missing a using directive or an assembly reference?)
This to me is a bit weird because if I parse the template instead it works fine.
So it is really only a performance issue but as it doesn't effect the site from running correctly.
Is there any reason why compiling (Razor.Compile(content, Name);) fails when parsing (Razor.Parse(content, model, this.Name)) Doesn't?
Thanks for the help :)
So I found a solution.
If I call a method in the namespace before the razor.Compile it seems to fix the issue.
I created a method called helloDll anywhere inside of the namespace that is failing.
public static void helloDll(){}
I call this before my compile
Bundler.cvStyleBundle.helloDll();
Razor.Compile(content, Name);
No more error :)
I think it has something to do with just in time dll loading and the fact that the dll is not loaded at the time of compile and because the compile happens in some weird lovely funky way it doesnt load the dll rather it just grabs all existing ones from the project :)

Definition mx.core:BitmapAsset could not be found. (with ant and FlashDevelop)

I saw this question:
mx.core::BitmapAsset could not be found
and the answer did not help.
I am compiling the code with ant and FlashDevelop and getting the error: Definition mx.core:BitmapAsset
If I compile normally in FlashDevelop without ant it works alright(no error).
I tried doing what they suggested in the answer and some other site and it did not work.
Namely:
I changed this xml field to true:
<static-link-runtime-shared-libraries>true</static-link-runtime-shared-libraries>
And attempted to import BitmapAsset from framework.swc
Please help me resolve this.
Either link to the flex library swc, or create your own mx.core.BitmapAsset that implements all the Interfaces BitmapAsset implements.

Joseki mysql sparql

I configured the joseki with mysql and also modified the joseki-config-sdb.ttl.
When I pass the select query I am getting the error like
The server encountered an internal error (com.hp.hpl.jena.sparql.core.Quad.isDefaultGraphIRI()Z)
that prevented it from fulfilling this request.
Please find the stack trace in the following
url http://pastie.org/1975277
Version of the build are
Joseki-3.4.4,sdb-1.3.4 and java 1.6 and the query is select * where {?s ?p ?o}
Please Let me know what I am missing here.
Thanks in advance
It looks to me as though you have incompatible versions of the .jar files. The exception you get is:
java.lang.NoSuchMethodError: com.hp.hpl.jena.sparql.core.Quad.isDefaultGraphIRI
NoSuchMethodError is thrown when the JVM has resolved the class name to a class object, but that class does not have the method requested. Code won't compile with this problem, so the fact that you're encountering it in compiled code means that you have mixed-up versions of the classes.
You need to ensure that the lib directory of your tomcat application has only Jena .jar files from the version of Joseki you are using. No older or newer versions, or duplicates. I suggest deleting everything in lib, then copying in just one set of Jena jars from your Joseki installation, and then any other .jar files your app needs.
Use arq-2.8.7. arq-2.8.8 do not have the missing method in the Quad class.