-
Notifications
You must be signed in to change notification settings - Fork 82
feat: move framework-info into build packages #4783
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
Conversation
|
This pull request adds or modifies JavaScript ( |
lukasholzer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add the same typescript config as for the other libraries that allows js files as well and adapt the files to the dist folders?
packages/framework-info/README.md
Outdated
| [](https://npmjs.org/package/@netlify/framework-info) | ||
| [](https://codecov.io/gh/netlify/framework-info) | ||
| [](https://github.com/netlify/framework-info/actions) | ||
| [](https://www.npmjs.com/package/@netlify/framework-info) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think they need to be updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you be open to having these just removed outright? Personally I'm not sure how useful they are as statuses here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's remove them :)
needed to add 'root' key in order to support invoking the build command from the repository root
At the moment we can't as there are no Typescript files in the package, and if we attempt to add the configuration files now we'll get an error about there being no input files 😞 I'd suggest doing this as a follow up pull request where we convert 1 file to Typescript (even if it's not fully typed) and add the configuration in as part of that (( edit: Ignore the above, it turned out that if I added |
… ep/add-framework-info
This reverts commit 812d123.
This reverts commit 6696e3b.
… ep/add-framework-info
| { | ||
| "extends": "../../tsconfig.base.json", | ||
| "compilerOptions": { | ||
| "noEmit": true /* Specify an output folder for all emitted files. */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Vite handles transpilation of TS files by default so this is left to allow for type checking prior to building with vite
Addressed comments and got another code review confirming the changes are good
danez
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to add it to the release-please configs:
https://github.com/netlify/build/blob/main/.release-please-manifest.json
https://github.com/netlify/build/blob/main/release-please-config.json
|
I think |
|
@danez Good point, I always forget about that |
lukasholzer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small comments
… ep/add-framework-info
Co-authored-by: Lukas Holzer <lukas.holzer@netlify.com>
… ep/add-framework-info
* docs: add deprecation notice depends on netlify/build#4783 * style: lint
… ep/add-framework-info
Co-authored-by: Lukas Holzer <lukas.holzer@netlify.com>
🎉 Thanks for submitting a pull request! 🎉
Summary
Fixes https://github.com/netlify/pod-ecosystem-frameworks/issues/330
Related issue: https://github.com/netlify/pillar-workflow/issues/1011
We want to eventually merge the functionality within
framework-infointobuild-infosince there's a great deal of overlap and having these 2 distinct projects is leading to a high maintenance burden.This is the first step in this process, which will lead to https://github.com/netlify/framework-info/ being archived.
For us to review and ship your PR efficiently, please perform the following steps:
we can discuss the changes and get feedback from everyone that should be involved. If you`re fixing a typo or
something that`s on fire 🔥 (e.g. incident related), you can skip this step.
passes our tests.
A picture of a cute animal (not mandatory, but encouraged)