Trailing semicolon (`;`) stripped before bundling, breaking `@import` and following bundled rule

### Link to the code that reproduces this issue or a replay of the bug https://github.com/JoelDSmith/next-bundling-bug ### To Reproduce 1. Clone this repository 2. Execute `npm install` 3. Execute `npm run build` 4. Execute `npm run start` 5. Navigate to [`http://localhost:3000`] 6. _Observe that one of the two documented issues have occurred_ (in both cases, the font rendered will be incorrect) 7. Repeat steps 3 through 6 until the other documented issue has occurred [`http://localhost:3000`]: http://localhost:3000 ### Current vs. Expected behavior _Indicator: when this issue is reproduced with the reproduction repository, the rendered text will be black until manually "fixed"._ It looks like a trailing semicolon (`;`) in SCSS files is stripped as part of transpilation of SCSS to CSS, before bundling occurs. For standalone files, this makes sense, as the trailing semicolon is optional. However, it doesn't make sense when these files are about to be bundled, because then they are no longer "standalone". For the reproduction repository, the transpiled and bundled output of the styling under [`src/app/lib`] ends up being: [//]: # (@formatter:off) ```css @import"https://fonts.googleapis.com/css2?family=Roboto+Condensed" :root{--validation:#be1a06} ``` [//]: # (@formatter:on) Screenshot additionally showing relevant CSS warnings in the browser console:  Screenshot showing the rendered page:  Simply manually re-adding the missing semicolon at the end of the `@import` line will fix the styling: [//]: # (@formatter:off) ```css @import"https://fonts.googleapis.com/css2?family=Roboto+Condensed"; :root{--validation:#be1a06} ``` [//]: # (@formatter:on) ![tra…