/tech/ - Technology★

// module.mjs
export function hello() {
  return "Hello";
}
// main.mjs
import ( hello ) from 'module'; // or './module'
let val = hello();  // val is "Hello";

>>1010462 (OP)

Presuming this is client-side JavaScript by the name of your files, all of your .js executes in the same global scope. It's considered bad practice to pollute the global scope with variables, so most frameworks will declare a single global variable to contain all of the bindings for your application. But if this is just some pet project, don't worry about it.

>>1010462 (OP)

// script_a.js
someVar = 140
// script_b.js
console.log(someVar + 60)
// page.html
<!-- ... -->
        <script src='script_a.js'><\script>
        <script src='script_b.js'><\script>
    </body>
</html>

When you declare your variable with “var” you're restricting it to that scripts context.

Like >>1010516 said, it is bad practice to put too much stuff in global so don't overuse it.

First >>1010575

but not using var would be an implicit global var which is invalid in strict mode (put '"use strict";' in the first line) so you should use window.x=1; for declaration.

The js files are run in the order they appear in in the HTML, so

<script src="page.js"></script>

<script src="page2.js"></script>

should work fine. No need for complicated extras or modules or classes or whatever.

>>1011114

Blame goyboard. For the “framework fags” argument, most people contextualise things as a debugging measure to prevent overwriting built-in browser variables, not because of frameworks.

>I can't even

Thanks tumblr

>>1011114

>not using mithril

It's like you hate fun.

dom manipulation

js file 1: document.writeln() an add an element with a specific id

js file 2: getElementById()

don't want it to be visible? use css for the id and use display: none

>>1011114

no-coder detected.

>>1011359

>>1011346

>>1011275

t. professional front end engineers

SO HOW THE FUCK DO YOU DO IT?????????????????????????????????????????????

If you declare it in global scope (inside no function) it will be accesible to the other file.

You could also make a global object like

let some_obj = {}

some_obj.x = 4

So you can put everything there as to not "contaminate" global scope too much.