This is a confusing design choice in TypeScript. In the short term you can work around it by specifying the output file: in main.ts specify the .js extension and path: import { testText } from ‘./module1.js’; alert(testText); This will pick up module.ts correctly, but output with the .js extension included. Note that you also need … Read more
One can add attributes to a script by applying filter ‘script_loader_tag’. Use add_filter(‘script_loader_tag”https://stackoverflow.com/questions/58931144/,”add_type_attribute’ , 10, 3); to add the filter. Define the callback function like the example given on the link above: function add_type_attribute($tag, $handle, $src) { // if not your script, do nothing and return original $tag if ( ‘your-script-handle’ !== $handle ) { … Read more
Working with CommonJS modules is pretty straight forward. You can only do default exports from CommonJS modules. import packageMain from ‘commonjs-package’; // Works import { method } from ‘commonjs-package’; // Errors This means that all commonjs exports will live on the packageMain object, and you need to dot in to the packageMain object to pickup … Read more
Ok so I found the solution here. Basically, had to add 2 things to the webpack config under module.rules: { test: /\.m?js/, type: “javascript/auto”, }, { test: /\.m?js/, resolve: { fullySpecified: false, }, },
By default any code in node_modules is ignored by babel-jest, see the Jest config option transformIgnorePatterns. I’ve also created a PR on your example repo, so you can see it working. While this works, I’ve found it to be extremely slow in real applications that have a lot of dependencies containing ES modules. The Jest … Read more
I went to the Node.JS forums and asked what could be the issue. Not a babel issue at all, just circular dependencies. For example: // A.js import B from ‘./B.js’ export default class A{} // B.js import A from ‘./A.js’ export default class B extends A{} Sorry there wasn’t nearly enough information to be able … Read more
Remove the line below from your statement export module Demo and use it like export class ViewModel { constructor(public test: string) { } } Edit: For namespace, just do something like namespace Demo { export class ViewModel { constructor(public test: string) { } } }
export should be static. For conditional exports CommonJS modules and exports can be used. It should be handled with ES6 modules this way: export let Foo; if (window.Foo === undefined) { Foo = class Foo { … } } else { Foo = window.Foo; } For platform-independent solution (this may not be equal to global … Read more
DOM has not changed in ES6, ES6 gives new features to JavaScript, that is all. In pure js exists event for dom loaded ( it is document ready from jquery equivalent ): document.addEventListener(“DOMContentLoaded”,function(){ //Your code here }); Modules working with DOM tree can have listener inside, or should be used after dom is ready. I … Read more
Here are the differences I have noted from various articles. If you want more details, read a complete article on the internet: Modules are singleton. They will be loaded and executed only once. Modules can use import and export. Modules are always executed in strict mode. All objects (class, const, function, let, or var) are … Read more