not so much error but consideration of structure, for components / CSS in old next version
13.0.3:
for page structure:
main-root/
pages/
main.tsx
localhost:3000/main
the index.js file imports the Main.tsx which makes for import path to become:
import main from '../components/Main
// all that has to be done then is to import the directory because it auto-infers index.js to be the source of truth
13.0.3:
for page structure:
main-root/
pages/
main.tsx
localhost:3000/main
in the main root there is a styles folder with sass and styled components files that correspond to page
It's not disorganized but I definitely prefer her react-express syntax of index.js importing the component to export
with Next's "file navigation" pages/file.tsx The file name comes from the .tsx file directly.
can we use a directory like so?
pages/
mkdir main/
main.tsx
index.js
main.css | main.scss
attempting to do: deploy. Nothing else.
not so much error but consideration of structure, for components / CSS in old next version 13.0.3: for page structure: main-root/ pages/ main.tsx localhost:3000/main
13.4.9 main-root/ app/ main/ page.tsx localhost:3000/main
bookmarking my team project class mates component/styling structure. (but for react-express)
main-root/ client/ src/ components/ Main/ Main.tsx/ main.css/ index.js
the index.js file imports the Main.tsx which makes for import path to become: import main from '../components/Main
// all that has to be done then is to import the directory because it auto-infers index.js to be the source of truth
13.0.3: for page structure: main-root/ pages/ main.tsx localhost:3000/main
in the main root there is a styles folder with sass and styled components files that correspond to page It's not disorganized but I definitely prefer her react-express syntax of index.js importing the component to export
with Next's "file navigation" pages/file.tsx The file name comes from the .tsx file directly.
can we use a directory like so? pages/ mkdir main/ main.tsx index.js main.css | main.scss
[5:08am]