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

Spike: Investigate rollup config options that should affect how we write output files #122

Closed
elycruz opened this issue Oct 7, 2023 · 1 comment
Labels
spike Marks ticket as an "Investigative" task triaged Deprecated - Use "groomed" instead.

Comments

@elycruz
Copy link
Owner

elycruz commented Oct 7, 2023

Currently we don't look for output.chunkFileNames, or related rollup config options before outputting transformed files - we should do this as it will allow users to leverage existing rollup knowledge to output files in the user wants to.

Acceptance Criteria

Investigate what rollup config options affect how files are output (including their names) and document them here.

Some options that immediately stick out:

  • output.entryFileNames
  • output.chunkFileNames
  • output.preserveModulesRoot

Resources:

https://rollupjs.org/configuration-options

Related issue: #65 .

@elycruz elycruz added triaged Deprecated - Use "groomed" instead. spike Marks ticket as an "Investigative" task labels Oct 7, 2023
@elycruz
Copy link
Owner Author

elycruz commented Aug 21, 2024

Closing this since rollup will take care of handling what needs to be done for output files - There are currently no conflicts with the rollup's currently defined output options that could interfere with the content generated by the [rollup-plugin-sass] plugin.

@elycruz elycruz closed this as completed Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spike Marks ticket as an "Investigative" task triaged Deprecated - Use "groomed" instead.
Projects
None yet
Development

No branches or pull requests

1 participant