Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

imports file organization #11

Open
asuh opened this issue Jul 25, 2024 · 0 comments
Open

imports file organization #11

asuh opened this issue Jul 25, 2024 · 0 comments

Comments

@asuh
Copy link
Owner

asuh commented Jul 25, 2024

I'm a fan of encapsulation and tend towards writing new CSS and Javascript as modular and component based.

For example, the script.js file should be a collection of import statements of any modular files in the /resources/scripts/ folder. If I review the scripts file, I'd see something like this:

import { feature } from './feature-file.js';
import { feature2 } from './feature2-file.js';

feature();
feature2();

Right now, the way that Vite builds the project, this doesn't work right.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant