Skip to content

imports file organization #11

@asuh

Description

@asuh

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions